emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: org-mode-email <emacs-orgmode@gnu.org>
Subject: org-cite: make 'suppress-author' a citation 'style'
Date: Sat, 24 Apr 2021 06:52:51 -0400	[thread overview]
Message-ID: <CAF-FPGObQL5hgYfdG=qNSguHti0cmWGZ+Fc77A5w1d+CO7rSew@mail.gmail.com> (raw)

Hi Nicolas,

As I was working on adding a function to generate the new cite syntax,
an idea occurred to me that I'd like to raise, that would simplify
this model and syntax.

I ran the idea by the pandoc list just to confirm my thinking was
reasonable, since that has a lot of experience using these plain-text


Let's review:

In org-cite, we have citations, and citation items.

Citations may have optional styles.

Citation items may have an optional "suppress-author" "variant",
indicated with a "-". So:


The idea:

This distinction is wrong, and we should treat "suppress-author" as a
citation style instead.

The result would be:


Or even can keep the shorthand:


In fact, with the change, could even remove it entirely

If you read the discussion in the pandoc list, there is mild, but I
don't think convincing, pushback.

Part of that pushback is an artifact of the fact that pandoc citations
don't have a notion of citation style, where you specify things like

OTOH, pandoc and (haskell) citeproc author John MacFarlane agrees that
in retrospect the pandoc decision was probably wrong, in part because
of another related issue.

Supress-author is a convention that CSL implementations settled on,
arguably a hack, to get around lack of explicit support for natbib
citet-like citations (though this is being added in the next version).

So to get "Doe (2019) argues" you would need to write "Doe [@doe19]"
in pandoc, for example.

But if you can do this in org-cite, "suppress-author" is no longer needed:

"[cite/text:@doe19] argues ..."

Both should probably be possible, but the textual (aka narrative)
style is what most users are looking for there IMO.

I think a positive side-effect is this model would match better LaTeX
output models (natbib and biblatex namely).



             reply	other threads:[~2021-04-24 10:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-24 10:52 Bruce D'Arcus [this message]
2021-04-24 12:28 ` org-cite: make 'suppress-author' a citation 'style' Bruce D'Arcus
2021-04-24 17:08 ` Nicolas Goaziou
2021-04-24 17:28   ` Bruce D'Arcus
2021-04-24 19:36     ` Bruce D'Arcus
2021-04-24 20:09       ` Nicolas Goaziou
2021-04-24 22:51         ` Bruce D'Arcus
2021-04-25  5:55           ` András Simonyi
2021-04-25 12:50             ` Bruce D'Arcus
2021-04-25 19:48               ` András Simonyi
2021-04-25 20:12                 ` Bruce D'Arcus
2021-04-26  7:53                   ` Denis Maier
2021-04-26  9:05                     ` Denis Maier
2021-04-26  9:34                     ` Joost Kremers
2021-04-26 11:36                       ` Bruce D'Arcus
2021-04-26  7:51     ` Richard Lawrence
2021-04-26  9:33       ` Bruce D'Arcus
2021-04-27  7:36         ` Richard Lawrence
2021-04-27  7:52           ` Denis Maier
2021-04-27  8:24             ` Richard Lawrence
2021-04-27 10:05             ` 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:

  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='CAF-FPGObQL5hgYfdG=qNSguHti0cmWGZ+Fc77A5w1d+CO7rSew@mail.gmail.com' \
    --to=bdarcus@gmail.com \
    --cc=emacs-orgmode@gnu.org \


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