From: "Bruce D'Arcus" <firstname.lastname@example.org>
To: "András Simonyi" <email@example.com>
Cc: org-mode-email <firstname.lastname@example.org>
Subject: Re: org-cite: make 'suppress-author' a citation 'style'
Date: Sun, 25 Apr 2021 16:12:08 -0400 [thread overview]
Message-ID: <CAF-FPGMSk45+Dcpk9HrkVNqxOwGCTNeR7e3W0fhpjoRH+8KkkA@mail.gmail.com> (raw)
On Sun, Apr 25, 2021 at 3:48 PM András Simonyi <email@example.com> wrote:
> Dear All,
> On Sun, 25 Apr 2021 at 14:50, Bruce D'Arcus <firstname.lastname@example.org> wrote:
> > How would you deal with these?
> > #+begin_example
> > [cite/-:@doe20; @doe21]
> > [cite/-:@doe20; see also @smith19]
> > [cite/text:@doe20; see also @smith19]
> > #+end_example
> > My thought is you want to treat the author of the first listed cite as
> > suppressed, or placed in-text in the last case, but that you wouldn't
> > touch the other author?
> yes, exactly -- since it's difficult to see (at least for me) how the
> context could supply the author information for the subsequent cites.
So the output for the first one would be:
..., and not:
(2020, Doe 2021)
As in, you would suppress the author not on the first cite (what you
wrote in the original reply), but the author of the first cite?
To me, that's the only wrinkle of having this a citation-level style;
that a processor would need to be smart enough to handle cases like
that, for output styles that require it.
But otherwise it's easier and more efficient for the user.
next prev parent reply other threads:[~2021-04-25 20:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-24 10:52 Bruce D'Arcus
2021-04-24 12:28 ` 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 [this message]
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
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 \
* 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).