From: John Carter Wood <woodjo-ZOsAvrTRSvuEhhMi0yms2Q@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Locator/label with roman numerals?
Date: Wed, 6 Jul 2022 11:41:02 -0700 (PDT) [thread overview]
Message-ID: <86c967e3-7933-42f5-b33b-f3a8764283ban@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1082 bytes --]
I've run into another curious issue (Pandoc 2.18).
The CSL-style I use has a label for locators ("at p.#" or "at pp. ##-##").
However, if the page numbers are in *Roman* numerals, the label does not
appear as it does with Arabic numerals.
The attached test .md file has two references and cites them with a page
number, one Arabic, one Roman. The results in the footnotes:
[image: locator-differences.png]
I have tried it with another CSL file that also uses p./pp. and the results
are the same.
Any idea what's going on? Is this related to the other locator issue I
raised with citeproc?:
https://github.com/jgm/citeproc/issues/107#issuecomment-1140252757
--
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/86c967e3-7933-42f5-b33b-f3a8764283ban%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1509 bytes --]
[-- Attachment #2: locator-differences.png --]
[-- Type: image/png, Size: 2082 bytes --]
[-- Attachment #3: locator-test.md --]
[-- Type: text/markdown, Size: 496 bytes --]
---
title: Locator test, Arabic versus Roman
csl: /home/john/Documents/csl/ieg-2-en-23.csl
references:
- type: book
id: doe1
author:
- family: Doe
given: Jane
issued:
date-parts:
- - 2022
title: A book title
publisher: 'Whatever press'
lang: en-GB
- type: book
id: doe2
author:
- family: Doe
given: Jane
issued:
date-parts:
- - 2022
title: A second book title
publisher: 'Whatever press'
lang: en-GB
...
Arabic [@doe1, 4]
Roman [@doe2, iv]
next reply other threads:[~2022-07-06 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 18:41 John Carter Wood [this message]
[not found] ` <86c967e3-7933-42f5-b33b-f3a8764283ban-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-06 20:35 ` Bastien DUMONT
2022-07-07 6:56 ` John Carter Wood
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=86c967e3-7933-42f5-b33b-f3a8764283ban@googlegroups.com \
--to=woodjo-zosavrtrsvuehhmi0yms2q@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).