From: "András Simonyi" <email@example.com>
To: Matt Price <firstname.lastname@example.org>
Cc: Org Mode <email@example.com>
Subject: Re: oc-csl/citeproc: suffixes in cite links
Date: Fri, 16 Jul 2021 23:21:00 +0200 [thread overview]
Message-ID: <CAOWRwxBQeXkFp8gzxdn62ptKGQb8kx9RVhufReGaXBgZJYz9jQ@mail.gmail.com> (raw)
yes, oc-csl has to extract the locator information from the suffix
because CSL processors like citeproc-el work with structured locator
data. To help this extraction, ocl-csl (similarly to citeproc-org and
I think pandoc) defines a list of locator expressions to be used in
the suffix (see the commentary of oc-csl or the citeproc-org README),
for chapter one can currently use "chap.", "chaps." or "chapter" --
hopefully replacing the citation with
[cite:@GentilcoreTastetomatoItaly2009 chap. 4] will fix the rendering,
On Fri, 16 Jul 2021 at 22:40, Matt Price <firstname.lastname@example.org> wrote:
> (cc:ing Andras in case this issue maybe comes from citeproc)
> I'm having some trouble with suffixes in cite: links when the oc-csl exporter is enabled, e.g. with something like this:
> #+cite_export: csl "/home/matt/src/styles/apa.csl"
> this cite:
> [cite:@GentilcoreTastetomatoItaly2009 ch4]
> is rendered as:
> (ch Gentilcore, 2009, p. 4)
> on export to HTML (in a document with no print_bibliography directive).
> BY contrast, ob-basic gives:
> (Gentilcore, David, 2009 ch4)
> Is oc-csl doing some extra work to process suffix, or is this likely an issue with citeproc, or alternatively am I just not really understanding what ought to be happening?
> Also, are other people seeing this same issue? I don't have a testing setup that would allow me to easily run emacs -Q (given how much has to be imported) so ... well, so, my apologies for not having done that.
next prev parent reply other threads:[~2021-07-16 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 20:40 oc-csl/citeproc: suffixes in cite links Matt Price
2021-07-16 21:21 ` András Simonyi [this message]
2021-07-16 21:34 ` Matt Price
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).