emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Denis Maier <denismaier@mailbox.org>
To: Bruce D'Arcus <bdarcus@gmail.com>,
	org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: [wip-cite-new] Initial implementation of `biblatex' citation processor
Date: Thu, 20 May 2021 15:56:57 +0200	[thread overview]
Message-ID: <d09020a9-8d8b-8d6a-2892-ecb6869a2d09@mailbox.org> (raw)
In-Reply-To: <CAF-FPGP7830CX8qCQeitKRkZSckpNCrjRVyWxLC-KWONJ90e1A@mail.gmail.com>

Am 20.05.2021 um 15:22 schrieb Bruce D'Arcus:
> On Thu, May 20, 2021 at 9:07 AM Denis Maier <denismaier@mailbox.org> wrote:
>>
>> Am 20.05.2021 um 12:36 schrieb Bruce D'Arcus:
>>> On Thu, May 20, 2021 at 4:18 AM Denis Maier <denismaier@mailbox.org> wrote:
> 
>>>> But maybe cite/plain or cite/basic or so?
>>>
>>> First, are those two suggestions just synonyms for cite/bare?
>>
>> Yes. Nicolas complained about cite/bare so I've thought cite/plain may
>> be nicer. (See autocite=plain) But the biblatex manual uses itself the
>> term "bare".
> 
> OK.
> 
> I don't care; I suggested "bare" because the earlier "alt" was super vague.
> 
>>> Or are you indeed suggesting completely changing the current logic of
>>> these styles and substyles? E.g "bare' substyle becomes rather a
>>> "plain" or "basic" style?
>>
>> I'm not really sure we need bare substyles at all. At least in biblatex
>> it's the basis for the other commands.
> 
> Though see my followup message on autocite config.
> 
> Does that change this discussion?

Why?

[...]

>>
>> #+begin_example
>> At the beginning Doe argues this and that (2020, p. 20). He goes on to
>> say blabla, see ibid., p. 23.
>> #+end_example
>>
>> In order to get the ibid., you'll need a \cite* instead of just a
>> \citeyear or so.
> 
> Shouldn't that example be covered in org-cite by, respectively ...
> 
> cite/year
> cite/bare (or plain)

Hmm, yes. The example was not ideal. Works better in an author title style:

#+begin_example
At the beginning Doe argues this and that (Title, p. 20). Later, Doe 
then says blabla, see ibid., p. 23.
#+end_example

You'd get that with
#+begin_example
At the beginning Doe argues this and that \parencite*[20]{doe}. Later, 
Doe then says blabla, see \cite*[23]{doe}.
#+end_example

cite/year => \citeyear won't work as this will just print the year 
without wrapping it in parentheses. It also won't trigger the ibid. in 
the next citation.
cite/bare = \cite would also work in that particular citation, but an 
author might remove the preceding sentence, which will make the ibid. 
disappear. You will then have a regular bare citation (= "Doe 2020", or 
"Doe, Title") instead of just the year or the title in parentheses.

> 
> ...?
> 
>>> And how would all of this map to natbib and citeproc? >
>>> The style+substyles really should work well across the output formats,
>>> and gracefully fallback if certain variants, particularly in biblatex,
>>> aren't available in other formats.
>>>
>>> Is that the case with your suggested changes?
>>
>> The problem is indeed portability between csl and biblatex (and natbib).
>> I think it's unavoidable that users who use biblatex specific commands
>> loose that to a certain degree. Fallback mappings should be added, of
>> course, but they will only get you so far. We should probably indicate
>> which commands work in all packages so users can make their decisions
>> consciously.
> 
> Yes, it seems highly likely that some of biblatex just won't fully
> work in other formats.
> 
> But ideally we'd limit that.

Absolutely!

Denis


  reply	other threads:[~2021-05-20 13:58 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 15:13 [wip-cite-new] Initial implementation of `biblatex' citation processor Nicolas Goaziou
2021-05-18 18:40 ` Bruce D'Arcus
2021-05-20  7:22   ` Rudolf Adamkovič
2021-05-20 10:38     ` Bruce D'Arcus
2021-05-19 10:03 ` Denis Maier
2021-05-19 10:43   ` Bruce D'Arcus
2021-05-19 12:33     ` Denis Maier
2021-05-19 13:44       ` Nicolas Goaziou
2021-05-19 13:50         ` Bruce D'Arcus
2021-05-19 14:31         ` Denis Maier
2021-05-19 14:46           ` Bruce D'Arcus
2021-05-19 15:23           ` Nicolas Goaziou
2021-05-20  8:04             ` Denis Maier
2021-05-20 10:36               ` Bruce D'Arcus
2021-05-20 11:56                 ` Bruce D'Arcus
2021-05-20 11:59                   ` Bruce D'Arcus
2021-05-20 13:24                   ` Denis Maier
2021-05-20 13:07                 ` Denis Maier
2021-05-20 13:22                   ` Bruce D'Arcus
2021-05-20 13:56                     ` Denis Maier [this message]
2021-05-20 14:11                       ` Bruce D'Arcus
2021-05-20 14:29                         ` Denis Maier
2021-05-20 15:14                           ` Bruce D'Arcus
2021-05-20 17:06                         ` Nicolas Goaziou
2021-05-20 21:51                           ` Denis Maier
2021-05-20 22:37                             ` Thomas S. Dye
2021-05-20 22:51                               ` Bruce D'Arcus
2021-05-21  0:07                                 ` Thomas S. Dye
2021-05-21 13:38                             ` Nicolas Goaziou
2021-05-20 13:08                 ` Denis Maier
2021-05-20 17:15               ` Nicolas Goaziou
2021-05-20 21:54                 ` Denis Maier
2021-05-21 13:29                   ` Nicolas Goaziou
2021-05-20 14:32             ` Denis Maier
2021-05-19 13:00 ` Denis Maier
2021-05-21 11:49 ` Bruce D'Arcus
2021-05-21 13:13   ` Nicolas Goaziou
2021-05-21 13:25     ` Bruce D'Arcus
2021-05-25 14:30       ` Bruce D'Arcus
2021-05-26 20:04         ` Nicolas Goaziou
2021-05-29 14:44 ` [org-cite, oc-csl] print_bibliography options Bruce D'Arcus
2021-05-29 15:15   ` Nicolas Goaziou
2021-05-29 16:03     ` Bruce D'Arcus
2021-05-29 16:30       ` Nicolas Goaziou
2021-05-31 18:10         ` András Simonyi
2021-05-31 21:54           ` Bruce D'Arcus

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=d09020a9-8d8b-8d6a-2892-ecb6869a2d09@mailbox.org \
    --to=denismaier@mailbox.org \
    --cc=bdarcus@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).