From: Russell Urquhart <russurquhart1@verizon.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Asciidoc --> ConTeXt for presentations
Date: Sun, 16 Oct 2016 10:11:33 -0500 [thread overview]
Message-ID: <20161016151132.GF522@verizon.net> (raw)
In-Reply-To: <87pon0d1ma.fsf@atmarama.com>
On Sun, Oct 16, 2016 at 12:33:49PM +0200, Saša Janiška wrote:
> Russell Urquhart <russurquhart1@verizon.net> writes:
>
> I do not (atm) have need for complex tables. Moreover, I’ve learnt that
> atm. Asciidoc is not supported input format for creating presentations
> with Pandoc…
While Pandoc does NOT input asciidoc, i use Asciidoc FX, as a previewer, and it also exports out to html, pdf, and i think you can get it to export to DocBook.
With DocBook, or html, you could take those into Pandoc and out to whatever you want. Kind of an extra step. But as i use Asciidoc FX all the time anyway, not that big of an extra step.
> …which practically means that I can just use markdown for my ligth
> writing (web stuff, small online articles etc.) and use ConTeXt for
> everything else where quality is required.
Yes, or, as i said above, use Asciidoc and Asciidoc FX, and then convert that to html, and then take that to Pandoc.
>
> Otoh, learning ConTeXt is going to be useful not only for presentations,
> but only for real book project which might arrive in the future…
IMO, if you are debating on learning Context, i think that would be a good use of your time.
fyi,
Russ
___________________________________________________________________________________
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-16 15:11 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
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 [this message]
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=20161016151132.GF522@verizon.net \
--to=russurquhart1@verizon.net \
--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).