From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: different syntax for docx comments in markdown
Date: Sat, 26 Aug 2017 15:25:13 -0700 [thread overview]
Message-ID: <20170826222513.GA45515@Johns-MacBook-Pro.local> (raw)
In-Reply-To: <cc015785-1692-4245-b55f-6b188706d15b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
It's because pandoc's markdown supports the bracket notation
for spans, while the others don't.
+++ tolot27 [Aug 26 17 12:59 ]:
> Hi.
> I wonder, why there are two different syntax for docx annotations in
> markdown if they are converted with "--track-changes=all". If I convert
> it to markdown_mmd or markdown_phpextra, the comments are rendered wit
> <span> tags. If I convert it to plain markdown, then a bracket notation
> with []{} is used. What's the rationale behind this?
> --
> Regards,
> Mathias
>
> --
> 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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [3]https://groups.google.com/d/msgid/pandoc-discuss/cc015785-1692-4245-
> b55f-6b188706d15b%40googlegroups.com.
> For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
> 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 3. https://groups.google.com/d/msgid/pandoc-discuss/cc015785-1692-4245-b55f-6b188706d15b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 4. https://groups.google.com/d/optout
prev parent reply other threads:[~2017-08-26 22:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-26 19:59 tolot27
[not found] ` <cc015785-1692-4245-b55f-6b188706d15b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-26 22:25 ` John MacFarlane [this message]
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=20170826222513.GA45515@Johns-MacBook-Pro.local \
--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).