public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Jiashu Zou <zjsdut-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: alphabetic characters preceded by backslash (\) are ignored
Date: Thu, 16 Sep 2021 09:42:52 -0700	[thread overview]
Message-ID: <m2fsu4lbeb.fsf@Johns-Air.hsd1.ca.comcast.net> (raw)
In-Reply-To: <353fea7b-e95d-4573-9614-693e4213eb92n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


Perhaps you could use the permalink feature on the dingus to give
us a specific example?  I tried \a\b and it worked fine.  But
perhaps you're using some non-latin characters?

Jiashu Zou <zjsdut-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> This behavior does not comply with the CommonMark spec. You can check at 
> the commonmark.js demo https://spec.commonmark.org/dingus/
>
> On Thursday, 16 September 2021 at 17:56:54 UTC+8 Jiashu Zou wrote:
>
>> alphabetic characters preceded by backslash (\) are ignored when 
>> converting from markdown to html. Where is this behavior documented? Is it 
>> possible to change?


  parent reply	other threads:[~2021-09-16 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16  9:56 Jiashu Zou
     [not found] ` <96580712-620a-4eaa-a4dc-129037bf5f3bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-16 10:01   ` Jiashu Zou
     [not found]     ` <353fea7b-e95d-4573-9614-693e4213eb92n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-16 10:18       ` Jiashu Zou
2021-09-16 16:42       ` John MacFarlane [this message]
     [not found]         ` <m2fsu4lbeb.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2021-09-17  1:23           ` amph...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
     [not found]             ` <089b0e7f-6b7d-4770-8f80-d9e9796178a6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-17  2:49               ` John MacFarlane

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=m2fsu4lbeb.fsf@Johns-Air.hsd1.ca.comcast.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    --cc=zjsdut-Re5JQEeQqe8AvxtiuMwx3w@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).