emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Denis Maier <denismaier@mailbox.org>
Cc: Bastien <bzg@gnu.org>, Org Mode List <emacs-orgmode@gnu.org>,
	Bruce D'Arcus <bdarcus@gmail.com>,
	Elias Bounatirou <elias.bounatirou@gmail.com>
Subject: Re: Suggestions for improved suffix parsing in oc-biblatex
Date: Thu, 30 Sep 2021 09:23:02 +0200	[thread overview]
Message-ID: <878rzele7d.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <f6d80843-da44-1c73-9d1d-078551903071@mailbox.org> (Denis Maier's message of "Wed, 29 Sep 2021 09:36:58 +0200")

Hello,

Denis Maier <denismaier@mailbox.org> writes:

> Well, there are even cases like this one:
>
> [cite:@doe especially 4, 12, and 15]
>
> [cite:@doe e.g. 4, 12, and 15]
>
> [cite:@doe among others 4, 12, and 15]
>
> [cite:@doe 4, but also 12 and 15]

AFAIU, all these cases are already handled by the locator parsing
algorithm used in oc-csl.el. If that is correct, my point is still the
same: there are very few cases where an explicit locator delimiter would
be necessary.

Note that for clarity, it would help to also specify, along with your
examples, what is the expected locator, and possibly the expected
output.


Regards,
-- 
Nicolas Goaziou


  reply	other threads:[~2021-09-30  7:24 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
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 [this message]
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=878rzele7d.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=bdarcus@gmail.com \
    --cc=bzg@gnu.org \
    --cc=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).