public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Melroch <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Escaping (was: Re: Missing bibliography)
Date: Fri, 11 Aug 2017 12:57:26 +0200	[thread overview]
Message-ID: <CADAJKhDoN4q1oXDWJzPX2KXvjVBakfEccWnLx-NM+w0A7KGhrg@mail.gmail.com> (raw)
In-Reply-To: <CADAJKhAxPoV+uyoJjynq_JbqZ+hccNcjiEcJXRpKb6Ruu8nZew-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2758 bytes --]

JGM wrote:
Perhaps pandoc should not allow reference link definitions
that start with `@`, since these conflict with citations?
Anyone have thoughts about this?  Someone should probably
put an issue on the bug tracker for this.
______________

That seems reasonable but please note that anything which contains literal
square brackets or asterisks has to be escaped anyway, so more or less
escaping will be required for many of us. Admittedly historical linguistics
and comparative philology (my onetime field, which I still interact with to
some extent) use more literal square brackets and asterisks than most, but
maybe the most reasonable solution would be section in the manual which
lists common cases where escaping is required.

Den 6 aug 2017 18:03 skrev "John MacFarlane" <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>:

Thanks (and apologies if I missed the files before).

Simple repro here:

```
hi[^fn3]

[^fn3]: [@Alhazen1572-qk, V.9]: "competentius est et rationabilius, ut
appareat supra perpendiculum, quam extra eam."
```

This yields an empty footnote.  Why?  Because the footnote
contains:

```
[@Alhazen1572-qk, V.9]: "competentius est et rationabilius, ut appareat
supra perpendiculum, quam extra eam."
```

which pandoc is parsing as a reference link definition!

Perhaps pandoc should not allow reference link definitions
that start with `@`, since these conflict with citations?
Anyone have thoughts about this?  Someone should probably
put an issue on the bug tracker for this.

In the mean time, a workaround is to backslash-escape the
colon:

   [@Alhazen1572-qk, V.9]\: "competentius...



-- 
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/ms
gid/pandoc-discuss/20170806160229.GA79285%40Johns-MBP.

For more options, visit https://groups.google.com/d/optout.

-- 
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/CADAJKhDoN4q1oXDWJzPX2KXvjVBakfEccWnLx-NM%2Bw0A7KGhrg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 4699 bytes --]

       reply	other threads:[~2017-08-11 10:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADAJKhAxPoV+uyoJjynq_JbqZ+hccNcjiEcJXRpKb6Ruu8nZew@mail.gmail.com>
     [not found] ` <CADAJKhAxPoV+uyoJjynq_JbqZ+hccNcjiEcJXRpKb6Ruu8nZew-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-11 10:57   ` Melroch [this message]
     [not found]     ` <CADAJKhDoN4q1oXDWJzPX2KXvjVBakfEccWnLx-NM+w0A7KGhrg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-12  6:30       ` 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=CADAJKhDoN4q1oXDWJzPX2KXvjVBakfEccWnLx-NM+w0A7KGhrg@mail.gmail.com \
    --to=melroch-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).