From: "Saša Janiška" <gour@atmarama.com>
To: ntg-context@ntg.nl
Subject: Re: Asciidoc --> ConTeXt for presentations
Date: Fri, 14 Oct 2016 19:30:51 +0200 [thread overview]
Message-ID: <87insuyh10.fsf@atmarama.com> (raw)
In-Reply-To: <20161014005257.GD522@verizon.net>
Russell Urquhart <russurquhart1@verizon.net> writes:
> About a year ago i really got into Asciidoc, and use it at my work for
> technical writing.
What are your output formats?
> For me, i had some Context files, that had, for example, footnotes,
> within footnotes, within footnots. This is very doable in
> Context. Asciidoc, currently, does not support this multiple levels of
> footnotes, so, as i expected, converting Context -> Asciidoc, was not
> able to do this.
Interesting…I also have need for footnotes within footnotes and hit that
barrier with rst/markdown or some other non-AsciiDoc format
recently. :-)
> My suggestions would be, as you are going from asciidoc to Context,
> make sure that you are happy with what you can do in asciidoc. Context
> should be able to readily handle a conversion from Pandoc.
Well, considering that ConTeXt can do much more than AsciiDoc, maybe for
regualr web content (blog posts, shorter articles etc.) I could simply
use Markdown without even going to AsciiDoc which is interesting option
only in case of being able to server as single-source format.
Sincerely,
Gour
--
The humble sages, by virtue of true knowledge, see with equal
vision a learned and gentle brāhmana, a cow, an elephant, a dog
and a dog-eater.
___________________________________________________________________________________
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-14 17:30 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 [this message]
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=87insuyh10.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).