From: "Saša Janiška" <gour@atmarama.com>
To: ntg-context@ntg.nl
Subject: Re: Asciidoc --> ConTeXt for presentations
Date: Thu, 13 Oct 2016 22:40:02 +0200 [thread overview]
Message-ID: <87lgxs6l0d.fsf@atmarama.com> (raw)
In-Reply-To: <6c0b6d61-7243-c88b-6f5a-c75770f5f3ab@gmx.es>
Pablo Rodriguez <oinos@gmx.es> writes:
Hello Pablo,
> since ConTeXt can handle XML natively, how about converting AsciiDoc to
> an XML presentation and then compiling the XML file with ConTeXt?
I must admit I was not aware of that.
AsciiDoc can convert to e.g. DocBook(5), but I wonder if/how ConTeXt
could handle it?
I’ve found something:
http://doctribute.com/blog/003-docbook-to-context-xsl-stylesheets-en.html
but this involves fiddling with XSL stylesheets, while Pandoc’s
covnersion from DocBook to ConTexT eliminates need for them.
Another option would be to jsut bite the bullet and learn ConTeXt
properly to be use for *all* serious writings which makes sense if I
consider that I *might* need to produce one presentation every 2 weeks
which is more the one hundred per year. :-O
In that case it would be nice to have bette/more support in my (Emacs)
editor, but that’s another topic for another thread after I did discover
related thread in AUCTeX list today. ;)
Sincerely,
Gour
--
The embodied soul may be restricted from sense enjoyment,
though the taste for sense objects remains. But, ceasing
such engagements by experiencing a higher taste,
he is fixed in consciousness.
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-10-13 20:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 10:35 Saša Janiška
2016-10-13 18:06 ` Pablo Rodriguez
2016-10-13 20:40 ` Saša Janiška [this message]
2016-10-13 21:07 ` Pablo Rodriguez
2016-10-13 22:03 ` Saša Janiška
2016-10-13 20:57 ` Mica Semrick
2016-10-13 21:12 ` Saša Janiška
2016-10-13 21:27 ` Pablo Rodriguez
2016-10-13 22:05 ` Saša Janiška
2016-10-14 8:10 ` Hans Hagen
2016-10-14 17:50 ` Saša Janiška
2016-10-14 18:54 ` Hans Hagen
2016-10-16 10:25 ` Saša Janiška
2016-10-16 11:07 ` Hans Hagen
2016-10-16 11:32 ` Saša Janiška
2016-10-16 14:16 ` Alan BRASLAU
2016-10-16 15:53 ` Saša Janiška
2016-10-13 21:20 ` Pablo Rodriguez
2016-10-15 16:54 ` Mica Semrick
2016-10-14 0:52 ` Russell Urquhart
2016-10-14 17:30 ` Saša Janiška
2016-10-15 14:09 ` Russell Urquhart
2016-10-16 10:33 ` Saša Janiška
2016-10-16 15:11 ` Russell Urquhart
2016-10-16 15:29 ` Saša Janiška
2016-10-16 17:36 ` Russell Urquhart
2016-10-16 18:02 ` Saša Janiška
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgxs6l0d.fsf@atmarama.com \
--to=gour@atmarama.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).