From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: DokuWiki writer strips away cs language specification for code block
Date: Thu, 13 Jul 2017 21:22:27 +0200 [thread overview]
Message-ID: <20170713192227.GC41791@macbook-air-2.home> (raw)
In-Reply-To: <ca40b0c2-5d35-4f0b-bd0d-ae57c0eb65c5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
+++ Jan Hamrský [Jul 13 17 07:33 ]:
> Could the translation manual look like a mapping from
> skylighting/pandoc supported languages (from pandoc) to DokuWiki
> supported languages (from documentation). Sample:
> [haskell] -> [haskell]
> [cs] -> [csharp]
> [] -> [6502acme]
> [mandoc] -> []
> My idea is that such list can be hopefully translated into Haskell
> structures.
Yes, this is what I had in mind. Actually, we don't need to
worry about languages that are supported in dokuwiki but not
pandoc. We just need a map from pandoc language names
(pandoc --list-highlight-languages) to dokuwiki names.
If you provide the map, I can do the Haskell part.
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/20170713192227.GC41791%40macbook-air-2.home.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2017-07-13 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 17:54 Jan Hamrský
[not found] ` <882d0e54-31a7-4fb3-bbe0-f8070513a2c6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-13 7:08 ` John MacFarlane
[not found] ` <20170713070842.GA38415-gd5emFPDCk1l5R22fHXGm0EMvNT87kid@public.gmane.org>
2017-07-13 14:33 ` Jan Hamrský
[not found] ` <ca40b0c2-5d35-4f0b-bd0d-ae57c0eb65c5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-13 19:22 ` John MacFarlane [this message]
[not found] ` <20170713192227.GC41791-gd5emFPDCk1l5R22fHXGm0EMvNT87kid@public.gmane.org>
2017-07-16 17:00 ` Jan Hamrský
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=20170713192227.GC41791@macbook-air-2.home \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/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).