From: "Jan Hamrský" <jan.hamrsky-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: DokuWiki writer strips away cs language specification for code block
Date: Wed, 12 Jul 2017 10:54:55 -0700 (PDT) [thread overview]
Message-ID: <882d0e54-31a7-4fb3-bbe0-f8070513a2c6@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2060 bytes --]
Hello,
I am having slight problem with pandoc functionality for DokuWiki and I am
not sure if it is a bug, missing feature or how just things are. So here I
am (as contribution document suggests).
Pandoc version
pandoc 1.19.2.1 (pandoc-types 1.17.0.5, texmath 0.9.4, skylighting 0.1.1.5)
Command line
pandoc -f markdown -t dokuwiki input.md
Used input
```cs
var answer = 42;
```
Output
<code>
var answer = 42;
</code>
Expected output
<code csharp>
var answer = 42;
</code>
As the pandoc markdown readers (except the strict one) understand the "cs"
and is also present in "--list-highlight-languages", It would be fine if
DokuWiki writer does a out of the box transformation using the alias for
the language (I guess this could be done with filter), because dokuwiki
accepts only "csharp" (documentation <https://www.dokuwiki.org/wiki:syntax>).
For end user like me
- No need to modify already written documents which use "cs" (accepted
eg. by Visual Studio Code).
- Out of the box functionality requires less hassle with setup before
usage.
- More compatibility between formats? With almost zero affects to
current usages?
So what you think? Is that missing feature (because it is something new) or
is that actually a bug (cs is understood by pandoc, but that is somehow
forgotten by dokuwiki writer)? I am aware of the filter program
possibilities here, but I am not myself Haskell developer and setup for
some machines could be painful.
--
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/882d0e54-31a7-4fb3-bbe0-f8070513a2c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 5032 bytes --]
next reply other threads:[~2017-07-12 17:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 17:54 Jan Hamrský [this message]
[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
[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=882d0e54-31a7-4fb3-bbe0-f8070513a2c6@googlegroups.com \
--to=jan.hamrsky-re5jqeeqqe8avxtiumwx3w@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).