ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Thangalin <thangalin@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Typesetting Markdown
Date: Sat, 25 May 2019 12:54:09 -0700	[thread overview]
Message-ID: <CAANrE7rwNu46Ck+y-xASx1pw7T0PCOGO69WM+xA3c4tWFGWK9A@mail.gmail.com> (raw)
In-Reply-To: <874l5kpf23.fsf@atmarama.com>


[-- Attachment #1.1: Type: text/plain, Size: 1050 bytes --]

> For Markdown --> ConTeXt usage, math is not my primary concern, but
> wonder what do you think about the Pandoc's "cons" as stated on
> pandoc-xhtml site, iow:
>
> * Main document language information.
> * Markup for language in text portions.
> * Any <div> or <span> elements markup.
>

For the document language, Pandoc provides language variables:

https://pandoc.org/MANUAL.html#language-variables

I haven't tried it, so I don't know if it'll handle variations on quotes or
hyphenation, but that strikes me as more a presentation layer aspect than a
content aspect. That is, ConTeXt (or LaTeX), given a language, is
responsible for showing the correct representation; whereas, Markdown is
responsible for the prose.

Intermixing languages is also possible, as per the above link.

Lastly, the above link also shows how to mark up div elements. I'll cover
how to create inline images later in the series---it requires a little bit
of Lua, depending on the complexity of the problem. See:

https://pandoc.org/MANUAL.html#divs-and-spans

Cheers!

[-- Attachment #1.2: Type: text/html, Size: 1607 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 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  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2019-05-25 19:54 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 [this message]
2019-05-26  9:18         ` Pablo Rodriguez
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=CAANrE7rwNu46Ck+y-xASx1pw7T0PCOGO69WM+xA3c4tWFGWK9A@mail.gmail.com \
    --to=thangalin@gmail.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).