From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Joseph Reagle
<joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>,
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Citation syntax description in manual
Date: Wed, 19 May 2021 10:21:13 -0700 [thread overview]
Message-ID: <m2r1i2iqra.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <d9397afc-78cb-9c47-5bb8-f5a88d096226-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
I gave it a try here:
https://github.com/jgm/pandoc/commit/d452155bcf158b790b0087d6d5c02cc3212c921c
Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> writes:
> On 21-05-18 14:54, John MacFarlane wrote:
>> You're right I think. If you want to propose a structure for
>> rewriting this, I'd consider it!
>
> I tried, but stopped short because I don't know the parsing logic that well. I had something like this:
>
> - Markdown citations begin with an "@" followed by an identifier; a
> sequence of citations are separated by semi-colons. (Does this ever
> conflict with numbered examples? I've never used the latter.)
> - A citation may be followed by optional pagination.
> - When citations appear within square brackets:
> - They are taken as in-text or a note citation, depending on the
> style.
> - Each citation within the semi-colon delimited list may have a
> prefix, locator, and suffix.
> - Citations that appear without brackets always render the names of the
> authors in-text.
> - pagination and a suffix may still follow within brackets.
> - complex identifiers and locators may be protected by inclusion within
> curly brackets.
> ... ?
next prev parent reply other threads:[~2021-05-19 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 15:49 Joseph Reagle
[not found] ` <28110ceb-e6ca-a40f-48ab-6e9a6d0137fd-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2021-05-18 18:54 ` John MacFarlane
[not found] ` <m28s4blvnx.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-05-18 20:58 ` Joseph Reagle
[not found] ` <d9397afc-78cb-9c47-5bb8-f5a88d096226-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2021-05-19 17:21 ` John MacFarlane [this message]
[not found] ` <m2r1i2iqra.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-05-19 17:32 ` Joseph Reagle
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=m2r1i2iqra.fsf@MacBook-Pro.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=joseph.2011-T1oY19WcHSwdnm+yROfE0A@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).