From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Backslashed back quote
Date: Sun, 2 Oct 2022 12:28:51 -0700 [thread overview]
Message-ID: <4FB6A2E3-4294-4517-BF12-793E0EEF6291@gmail.com> (raw)
In-Reply-To: <874jwms6e7.fsf-hcDgGtZH8xNBDgjK7y7TUQ@public.gmane.org>
Backtick can have a special meaning in RST, so pandoc escapes it in many cases.
It uses a simple heuristic to avoid escaping backticks that clearly can't have
the special meaning (word-internal).
> On Oct 2, 2022, at 6:26 AM, Denis Bitouzé <denis.bitouze@univ-littoral.fr> wrote:
>
> Le 02/10/22 à 11h49, Denis Bitouzé a écrit :
>
>> is there any reason for the last back quote below to be backslashed?
>>
>> ┌────
>> │ $ pandoc -f dokuwiki -t rst <<< ':foo:`bar <baz>`'
>> │ :foo:`bar <baz>\`
>> └────
>
> Cleaner examples:
>
> ┌────
> │ $ pandoc -f dokuwiki -t rst <<< 'a`b'
> │ a`b
> │ $ pandoc -f dokuwiki -t rst <<< 'a`'
> │ a\`
> │ $ pandoc -f dokuwiki -t rst <<< 'a` '
> │ a\`
> │ $ pandoc -f dokuwiki -t rst <<< 'a` b'
> │ a\` b
> └────
>
> The back quotes seem to not be escaped (backslashed) if and only if they
> are followed by a non empty string.
> --
> Denis
>
> --
> 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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/874jwms6e7.fsf%40example.com.
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/4FB6A2E3-4294-4517-BF12-793E0EEF6291%40gmail.com.
prev parent reply other threads:[~2022-10-02 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 9:49 Denis Bitouzé
[not found] ` <878rlysggr.fsf-hcDgGtZH8xNBDgjK7y7TUQ@public.gmane.org>
2022-10-02 13:26 ` Denis Bitouzé
[not found] ` <874jwms6e7.fsf-hcDgGtZH8xNBDgjK7y7TUQ@public.gmane.org>
2022-10-02 19:28 ` 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=4FB6A2E3-4294-4517-BF12-793E0EEF6291@gmail.com \
--to=fiddlosopher-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).