From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: HTML to Markdown and >/< entities
Date: Sun, 30 Jul 2017 13:42:33 -0700 [thread overview]
Message-ID: <20170730204232.GF11715@Johns-MacBook-Pro.local> (raw)
In-Reply-To: <CA+u6gbzgquNuuGXLdsCtcdo+JhS2BchV9zQbyJNmaRVa7_UsVQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
We need to escape `<` and `>` in general, since these
can have special meanings in Markdown (autolinks,
raw HTML).
We could use either `\<` or `<`; we used the latter
because the former doesn't work with the original
Markdown.pl and derivatives (such as showndown,
python markdown, etc.).
I think it would make sense, though, to use `\<`
and `\>` when `all_symbols_escapable` is set.
I'm going to implement that change.
next prev parent reply other threads:[~2017-07-30 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 10:14 Benjamin Ullrich
[not found] ` <6e17b71f-4ce2-4e88-9bc3-fbdbb4d74365-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-28 11:53 ` Ivan Lazar Miljenovic
[not found] ` <CA+u6gbzgquNuuGXLdsCtcdo+JhS2BchV9zQbyJNmaRVa7_UsVQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-07-30 20:42 ` John MacFarlane [this message]
[not found] ` <20170730204232.GF11715-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-08-01 22:10 ` Melroch
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=20170730204232.GF11715@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).