From: "Clément Aubert" <aubert.clement-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Role of pandoc, citeproc and csl style with prefix, locator, and suffix
Date: Sat, 23 Jul 2022 09:49:30 -0400 [thread overview]
Message-ID: <CAPGHSey6b=EQ8ig-jMSc5GSa95zEmCfYEr9yrOfJ=wbqzEkHcQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]
Good morning,
The following
[@item1 Section 1]
[@item1 p. 12]
[@item1{Definition 12}]
will give with the default style
(Doe 2005, sec. 1) (Doe 2005, 12) (Doe 2005, Definition 12)
but with e.g. elsevier-with-titles.csl (
https://github.com/citation-style-language/styles/blob/master/elsevier-with-titles.csl
) I will get
[1] [1] [1]
that is, in this latter case, the locators are just "gobbled up". *I would
like to have that style correctly use the locators.*
The documentation reads
> By default, pandoc will use the Chicago Manual of Style
> <https://chicagomanualofstyle.org> author-date format.
>
but I couldn't find which actual csl file is used. This one (
https://www.zotero.org/styles/chicago-author-date-16th-edition ) indeed has
a segment
<macro name="locators">
that is absent from the elsevier-with-titles.csl: is the .csl file the
right place to add this behaviour?
Thanks!
Clément.
--
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/CAPGHSey6b%3DEQ8ig-jMSc5GSa95zEmCfYEr9yrOfJ%3DwbqzEkHcQ%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2857 bytes --]
next reply other threads:[~2022-07-23 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 13:49 Clément Aubert [this message]
[not found] ` <CAPGHSey6b=EQ8ig-jMSc5GSa95zEmCfYEr9yrOfJ=wbqzEkHcQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-24 23: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='CAPGHSey6b=EQ8ig-jMSc5GSa95zEmCfYEr9yrOfJ=wbqzEkHcQ@mail.gmail.com' \
--to=aubert.clement-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).