From: Denis Maier <denis.maier.lists-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: using "ff." for "following pages" results in "p." instead of "pp."
Date: Wed, 2 Sep 2020 23:05:24 +0200 [thread overview]
Message-ID: <9a8f155b-a677-8ccb-e534-6ff8209e5f2f@mailbox.org> (raw)
In-Reply-To: <m2v9gwrpmj.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
Currently, CSL has a couple of options to collapse page-ranges, but I'm
not aware of a way to collapse "12-13" to "12f." or "12-25" to "12ff."
(Maybe that's just me though...; I'll check.)
Regarding open-ended ranges like "12ff.": I've just had a quick test
with Word/Zotero: a locator like "12ff." is not interpreted as an
open-ended page range, but "12-" is. The result is "Doe, 2020, pp. 12-"
Pandoc-citeproc has a slightly different behavior:
[@doe, 12-] => "Doe, 2020, pp. 12" (the "-" disappears)
[@doe, 12-ff] => "Doe, 2020, pp. 12-ff"
A filter could be used here to do the necessary polishing.
Anyway, I think the cleanest solution would be to add support for this
in CSL. I'll open an issue on Gihub to discuss what can be done.
Am 02.09.2020 um 20:37 schrieb John MacFarlane:
> I'd be interested to hear from CSL devs about how this should be handled.
>
> JL <linkersdoerfer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
>> Is it possible to have pandoc-citeproc interpret a locator like
>>
>> 12ff
>>
>> as multiple pages? Currently, I get
>>
>> p. 12ff
>>
>> while
>>
>> pp. 12ff
>>
>> would be correct.
>>
>> --
>> 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/ee53a720-612b-4864-9676-3311eec6dcben%40googlegroups.com.
prev parent reply other threads:[~2020-09-02 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 15:46 JL
[not found] ` <ee53a720-612b-4864-9676-3311eec6dcben-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-02 18:37 ` John MacFarlane
[not found] ` <m2v9gwrpmj.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-09-02 21:05 ` Denis Maier [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=9a8f155b-a677-8ccb-e534-6ff8209e5f2f@mailbox.org \
--to=denis.maier.lists-cl+vpiynx/1afugrpc6u6w@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).