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:07:04 +0200	[thread overview]
Message-ID: <8959af45-54f3-da9f-5af2-e23a64bebadd@mailbox.org> (raw)
In-Reply-To: <CAF-FPGOZNo4tnj3Zt0CRufm9GN2uVhoujzhve-gmUPZwFR7cqQ@mail.gmail.com>

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:
> 
>> Could be, but also [cite/text/bare] or cite/foot/bare or cite/super/bare
>> as they all are essentially just wrappers around the plain cite command
>> (textcite is a bit different, but parencite and footcite really have the
>> same definition as cite, the only difference being that they add some
>> kind of wrapper.)
>> So, starting from parencite and then removing the wrapper would my logic
>> instead ;-)
>> 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".


> 
> 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.
But anyway: My first suggestion was cite/bare, and the reasoning behing 
that was:
cite: is equal to cite/default:
cite/default is equal to cite/auto
cite/auto is equal to cite/parens or cite/note
cite/bare could be understood as cite/auto/bare, which is cite/note/bare 
or cite/parens/bare

I just don't really like the notion of first adding a wrapper just to 
remove it afterwards.

> 
> If yes, I need to think on this more.
> 
>> |-----------+---------------+--------------|
>> | parens    | noauthor-caps | Parencite*   |
>> | parens    | noauthor      | parencite*   |
>> | parens    | caps          | Parencite    |
>> | parens    |               | parencite    |
>> |-----------+---------------+--------------|
>> | plain     | noauthor-caps | Cite*        |
>> | plain     | noauthor      | cite*        |
>> | plain     | caps          | Cite         |
>> | plain     |               | cite         |
>> |-----------+---------------+--------------|
> 
> Second, I don't understand some of the above.
> 
> Why "noauthor", for example? Is that not handled currently with a "year" style?
> 
> cite/year/caps

First of all, what does capitalization of a number mean? There's no 
\Citeyear in biblatex, after all.
But that aside, \citeauthor, \citetitle and \citeyear are lower level 
commands than \cite*{}.
\cite* will work in author-date styles and in author-title styles. It 
will either print the date or the title. When using \citeyear directly 
you cannot easily switch to a different style. And: citeyear etc. don't 
use the internal trackers (ibid., idem., etc.).

#+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.

> 
> 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.

Perhaps we should start thinking from the high level commands:

| CSL             | biblatex                            |
|-----------------+-------------------------------------|
| default         | autocite (=parencite or footcite)   |
| in-text         | textcite                            |
| suppress author | autocite* (=parencite* or footcite* |
|-----------------+-------------------------------------|

FWIW, footcite* does not exist in all styles, so it will just behave 
like the regular footcite.

> 
> Bruce
> 
> PS - I hadn't yet integrated sub-styles in this table, but we probably
> need a table that does that.
> 
> https://github.com/bdarcus/bibtex-actions/wiki/Org-cite
> 
> 



  parent reply	other threads:[~2021-05-20 13:08 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 [this message]
2021-05-20 13:22                   ` Bruce D'Arcus
2021-05-20 13:56                     ` Denis Maier
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=8959af45-54f3-da9f-5af2-e23a64bebadd@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).