ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Typesetting Markdown
Date: Sun, 26 May 2019 11:18:52 +0200	[thread overview]
Message-ID: <12635629-47d9-028b-c0fb-458f793afa72@gmx.es> (raw)
In-Reply-To: <CAANrE7rwNu46Ck+y-xASx1pw7T0PCOGO69WM+xA3c4tWFGWK9A@mail.gmail.com>

On 5/25/19 9:54 PM, Thangalin wrote:
>[...]
> For the document language, Pandoc provides language variables:
>
> https://pandoc.org/MANUAL.html#language-variables
> [...]
> Intermixing languages is also possible, as per the above link.

As far as I can remember, neither of them were available when I wrote
that (for ConTeXt, I mean).

I think that TeX output is the main problem in the development of
pandoc, because XML is so different from TeX.

But this is another issue and it doesn’t belong here.

Looking forward to seeing your sources and your output documents!

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  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2019-05-26  9:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23  5:18 Thangalin
2019-05-23  5:44 ` Jan U. Hasecke
2019-05-23  6:08 ` Saša Janiška
2019-05-24  3:37   ` Thangalin
2019-05-24  6:00     ` Saša Janiška
2019-05-25 19:54       ` Thangalin
2019-05-26  9:18         ` Pablo Rodriguez [this message]
2019-05-25 12:45     ` Pablo Rodriguez

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=12635629-47d9-028b-c0fb-458f793afa72@gmx.es \
    --to=oinos@gmx.es \
    --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).