From: Denis Maier <denismaier@mailbox.org>
To: Org Mode List <emacs-orgmode@gnu.org>,
Elias Bounatirou <elias.bounatirou@gmail.com>
Subject: Re: Suggestions for improved suffix parsing in oc-biblatex
Date: Mon, 20 Sep 2021 13:08:41 +0200 [thread overview]
Message-ID: <2d4dab38-0eaa-82bd-fb1e-a3b19a06af4c@mailbox.org> (raw)
In-Reply-To: <a73cc4ec-fee0-4d58-899a-3fd55b66fc59@mailbox.org>
Bump
Am 08.09.2021 um 15:37 schrieb Denis Maier:
> Hi,
>
> I think the suffix parsing in oc-biblatex could be improved. Consider
> this example:
>
> ====================================
> #+cite_export: biblatex authoryear
>
> [cite:@doe 4]
>
> [cite:@doe 4, with some more text]
> =====================================
>
> This gives us
> =====================================
> \autocite[4]{doe}
>
> \autocite[4, with some more text]{doe}
> =====================================
>
> The problem is that biblatex will add a label if the suffix consists
> only of a number, a range of numbers, or a list of numbers. So
> \autocite[4]{doe} will result (Doe 2021, p. 4). However, \autocite[4,
> with some more text]{doe} results in (Doe 2021, 4, with some more text).
> In this special case you'd have to help biblatex:
> \autocite[\pnfmt{4}, with some more text]{doe}
> => (Doe 2021, p. 4, with some more text)
>
> FWIW, pandoc's citeproc already has some support for this. There you can
> use braces to specify a locator in a complex suffix. Like so:
> [cite:@doe {4}, with some more text]
>
> I don't know how complex that is, but that would be a great addition.
>
> Denis
>
>
next prev parent reply other threads:[~2021-09-20 11:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 13:37 Suggestions for improved suffix parsing in oc-biblatex Denis Maier
2021-09-20 11:08 ` Denis Maier [this message]
2021-09-26 11:12 ` Bastien
2021-09-28 11:41 ` Nicolas Goaziou
2021-09-28 12:16 ` Bruce D'Arcus
2021-09-29 6:30 ` Nicolas Goaziou
2021-09-29 7:36 ` Denis Maier
2021-09-30 7:23 ` Nicolas Goaziou
2021-09-30 16:14 ` Denis Maier
2021-10-01 8:42 ` Nicolas Goaziou
2021-10-01 8:46 ` Denis Maier
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2d4dab38-0eaa-82bd-fb1e-a3b19a06af4c@mailbox.org \
--to=denismaier@mailbox.org \
--cc=elias.bounatirou@gmail.com \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).