From: "Saša Janiška" <gour@atmarama.com>
To: ntg-context@ntg.nl
Subject: Re: Asciidoc --> ConTeXt for presentations
Date: Fri, 14 Oct 2016 00:03:50 +0200 [thread overview]
Message-ID: <87d1j37vp5.fsf@atmarama.com> (raw)
In-Reply-To: <82d54795-51b7-05d6-b2b5-783437fe51d8@gmx.es>
Pablo Rodriguez <oinos@gmx.es> writes:
> this feature makes ConTeXt much superior than LaTeX, but not all TeX
> users are aware of this jewel.
:-)
> Sure it can handle it, but I wonder whether this would make sense. (I
> mean, does DocBook handle slides?)
That’s valid point…I was also thinking about it and found something:
http://docbook.org/schemas/5x-custom.html#slides
> But this approach allows me to generate (with pandoc) PDF and ePub
> documents from exactly the same source. I only need to write the style
> files for each.
That was suggested to me at the beginning of year when I was asking
aobut ConTeXt vs Beamer, but the problem is it handles only Markdown
which is too simple for my general writing and when/if one uses
extensions, then it’s really a mess…
> ConTeXt XML input will afford you the markup, but you’ll have to know
> how to deal with the slides in ConTeXt :-).
That’s true…I’m simply trying, like you, to have AsciiDoc as
single-source format and then publish content on the web
(static-site-generator), producing high-quality PDF and/or ePub.
Sincerely,
Gour
--
Whenever and wherever there is a decline in religious practice,
O descendant of Bharata, and a predominant rise of irreligion —
at that time I descend Myself.
___________________________________________________________________________________
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 22:03 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
2016-10-13 21:07 ` Pablo Rodriguez
2016-10-13 22:03 ` Saša Janiška [this message]
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=87d1j37vp5.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).