From: Robert Goulding <r.d.goulding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Missing biblio
Date: Sun, 6 Aug 2017 14:33:36 -0700 (PDT) [thread overview]
Message-ID: <883d77fb-5e85-4b8a-8efe-96e629ff032a@googlegroups.com> (raw)
In-Reply-To: <20170806160229.GA79285@Johns-MBP>
[-- Attachment #1.1: Type: text/plain, Size: 1592 bytes --]
Thank you! I will backslash the colons in the file as a fix for now. -
Robert.
On Sunday, August 6, 2017 at 12:02:43 PM UTC-4, John MacFarlane wrote:
>
> 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/msgid/pandoc-discuss/883d77fb-5e85-4b8a-8efe-96e629ff032a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2241 bytes --]
next prev parent reply other threads:[~2017-08-06 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 19:59 Robert Goulding
[not found] ` <185cf47c-84e5-41b3-8a88-ba092bc4f191-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-05 17:06 ` John MacFarlane
2017-08-06 14:17 ` Robert Goulding
[not found] ` <b1e81aba-1be2-4b68-b76a-1147c0ca0472-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-06 14:18 ` Robert Goulding
[not found] ` <93a2e736-ac22-48d5-abe6-78e002859383-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-06 16:02 ` John MacFarlane
2017-08-06 21:33 ` Robert Goulding [this message]
[not found] ` <883d77fb-5e85-4b8a-8efe-96e629ff032a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-06 21:52 ` Robert Goulding
[not found] ` <08b2ce82-4d36-4e6b-be2c-b8fb0dddec97-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-07 5:08 ` John MacFarlane
[not found] ` <20170807050821.GC81152-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-08-10 13:45 ` Robert Goulding
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=883d77fb-5e85-4b8a-8efe-96e629ff032a@googlegroups.com \
--to=r.d.goulding-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).