From: r.ermers@hccnet.nl
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Module for Markdown: any volunteer to make a ConTeXt interface?
Date: Sun, 7 May 2017 23:33:30 +0200 [thread overview]
Message-ID: <EDC17549-6E96-4AE4-8E13-0794235933ED@hccnet.nl> (raw)
In-Reply-To: <CADs1X4_aTdcmXKdC2rOnyMkRT5Qbeumcd-vT=o_ae0iBx0cYDg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 4010 bytes --]
I recently finished a book project in multimarkdown, which I converted to LaTeX (I could not use ConTeXt because of its limited bibliographical functions in comparison to BibLatex).
It worked fine. If I remember correctly, I preferred multimarkdown over markdown for more possibilities regarding tables.
Robert
> Op 6 mei 2017, om 13:16 heeft Brian Ballsun-Stanton <brian@fedarch.org> het volgende geschreven:
>
> For what it's worth, the folks I work with would find it very valuable. Our team currently composes on drive and I have to kick things in various ways via pandoc to get it into our ConTeXt server (multi-user editing with floobits is ... kinda neat). Reducing complexity of that would be wonderful. I also use the md mechanism in journal publishing (https://github.com/sx-archipelagos/sxa <https://github.com/sx-archipelagos/sxa>) -- and would find it very useful there.
>
> (The other route that would be very useful here is any paperpile integration, but that's rather outside the scope of this discussion).
>
> On 6 May 2017 at 18:28, Hans Hagen <pragma@wxs.nl <mailto:pragma@wxs.nl>> wrote:
> On 5/5/2017 9:54 PM, Aditya Mahajan wrote:
> On Thu, 4 May 2017, Mojca Miklavec wrote:
>
> Hi,
>
> There's a really nice module for processing markdown:
> https://github.com/Witiko/markdown <https://github.com/Witiko/markdown>
> that has been presented during the TUG meeting and is included in TeX
> Live.
>
> This is a fork of luamark (by the author of pandoc). Wouldn't it be
> better to provide an interface around that? Is it simply providing a tex
> interface around luamark or are there any changes in the parser as well.
>
> Any idea how it compares with the markdown parser in m-markdown already
> included in ConTeXt?
>
> that one was written when i tested some other lua thing that was very slow/inefficient .. irr some of the improved code was backported but as i never use markdown i didn't keep track of it (maybe some day i'll pick up that tread for mixed source coding or so)
>
> Hans
>
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl <http://www.pragma-ade.nl/> | www.pragma-pod.nl <http://www.pragma-pod.nl/>
> -----------------------------------------------------------------
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl <mailto:ntg-context@ntg.nl> / http://www.ntg.nl/mailman/listinfo/ntg-context <http://www.ntg.nl/mailman/listinfo/ntg-context>
> webpage : http://www.pragma-ade.nl <http://www.pragma-ade.nl/> / http://context.aanhet.net <http://context.aanhet.net/>
> archive : https://bitbucket.org/phg/context-mirror/commits/ <https://bitbucket.org/phg/context-mirror/commits/>
> wiki : http://contextgarden.net <http://contextgarden.net/>
> ___________________________________________________________________________________
>
>
>
> --
>
>
> <http://fedarch.org/>
>
> Brian Ballsun-Stanton Ph.D.
> FAIMS Project <http://fedarch.org/> - Data Architect <http://www.mendeley.com/profiles/brian-ballsun-stanton/>
> brian@fedarch.org <mailto:brian@fedarch.org> 0479 178 749
>
>
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 8587 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 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
___________________________________________________________________________________
next prev parent reply other threads:[~2017-05-07 21:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 20:55 Mojca Miklavec
2017-05-05 19:54 ` Aditya Mahajan
2017-05-05 21:12 ` Mojca Miklavec
2017-05-05 22:04 ` Vít Novotný
2017-05-06 8:28 ` Hans Hagen
2017-05-06 11:16 ` Brian Ballsun-Stanton
2017-05-07 21:33 ` r.ermers [this message]
2017-12-05 18:20 ` Gour
2017-12-23 21:44 ` Rik Kabel
2017-12-23 22:04 ` Alan Braslau
2017-12-24 15:01 ` Gour
2017-12-24 17:21 ` Alan Braslau
2017-05-06 15:42 ` John Culleton
2017-05-06 15:51 ` Mica Semrick
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=EDC17549-6E96-4AE4-8E13-0794235933ED@hccnet.nl \
--to=r.ermers@hccnet.nl \
--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).