From: Mica Semrick <mica@silentumbrella.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Asciidoc --> ConTeXt for presentations
Date: Sat, 15 Oct 2016 09:54:25 -0700 [thread overview]
Message-ID: <1F13A2C6-7C8A-4074-AF25-8CCD62AA3AE9@silentumbrella.com> (raw)
In-Reply-To: <bc35bd28-304b-8fd5-7947-da0de23ba49a@gmx.es>
[-- Attachment #1.1: Type: text/plain, Size: 1114 bytes --]
Sorry! I often transpose numbers. Thanks for the correction.
-m
On October 13, 2016 2:20:13 PM PDT, Pablo Rodriguez <oinos@gmx.es> wrote:
>On 10/13/2016 10:57 PM, Mica Semrick wrote:
>> From the pandoc github issues page, looks like they're working on
>> asciidoc. See issue 1465 in the pandoc repo.
>
>Sorry, I didn’t know that AsciiDoc wasn’t supported by pandoc as input
>format.
>
>But it isn’t relevant where the HTML cocde comes from to be handled by
>ConTeXt (as long it is valid XML).
>
>BTW, the right number issue is
>https://github.com/jgm/pandoc/issues/1456.
>
>Pablo
>--
>http://www.ousia.tk
>___________________________________________________________________________________
>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
>___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 1076 bytes --]
[-- Attachment #2: Type: text/plain, Size: 489 bytes --]
___________________________________________________________________________________
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-15 16:54 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 [this message]
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=1F13A2C6-7C8A-4074-AF25-8CCD62AA3AE9@silentumbrella.com \
--to=mica@silentumbrella.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).