From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: Emmanuel Charpentier <emm.charpentier@free.fr>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-cite: how to include a cite with no key?
Date: Tue, 20 Jul 2021 07:41:53 -0400 [thread overview]
Message-ID: <CAF-FPGMWgjHMkDvZeB5EP=C1LnGQAZCs9=+MikpgOmNu4t_OiQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ51ETr16EKuV1OnZNFL_oVONsH5bLO65YM72_7kLFMKe9Obew@mail.gmail.com>
On Mon, Jul 19, 2021 at 8:48 PM John Kitchin <jkitchin@andrew.cmu.edu> wrote:
>
> On Mon, Jul 19, 2021 at 7:28 PM Emmanuel Charpentier <emm.charpentier@free.fr> wrote:
>>
>> > In natbib there is \citetext{priv.\ comm.} which is used to add a
>> > textual citation to the bibliography that doesn't have a key
>> > associated with it.
>>
>> Hmmm... why should you bother to reference a personal communication ?
>> Such private communications may be mentionned in the text (possibly by
>> a footnote) but can't be properly referenced (since there is nothing to
>> refer to). If you feel that this communication must be referred to, you
>> should give it some (written) support and (properly) reference this
>> support.
>
>
> Who is to say why someone would bother. It is a command on page two of
> http://tug.ctan.org/macros/latex/contrib/natbib/natnotes.pdf that one can use.
>
> It is also possible to use \nocite{*} as a cite, which includes all
> references from a bibliography, and yet contains no key. Even funnier in a way is \nocite{key} which just adds entries to the bibliography, but does not cite them in the body of a document.
>
> Footnotes are not always allowed in publications, and for various reasons not worth defending, in proposals one might want to put this in the references because of space limitations.
If not a footnote, a parenthetical note?
What's the value of a citation and bibliography processor handling
formatting here?
Certainly in the CSL world, this has never been supported, and I don't
ever recall it ever coming up (though I'm sure someone on the Zotero
forum raised it at some point).
I will point out the syntax discussion long predates my participation
in the last year or so.
Perhaps it was raised at some point in the past and rejected?
If not raised, it's not surprising it's not supported now.
Bruce
next prev parent reply other threads:[~2021-07-20 11:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 23:28 org-cite: how to include a cite with no key? Emmanuel Charpentier
2021-07-20 0:47 ` John Kitchin
2021-07-20 6:55 ` Matt Price
2021-07-20 7:31 ` Emmanuel Charpentier
2021-07-21 18:54 ` Matt Price
2021-07-20 7:25 ` Emmanuel Charpentier
2021-07-20 11:41 ` Bruce D'Arcus [this message]
2021-07-20 12:50 ` Denis Maier
2021-07-20 13:50 ` Bruce D'Arcus
2021-07-20 14:12 ` Denis Maier
2021-07-20 12:38 ` Stefan Nobis
-- strict thread matches above, loose matches on Subject: below --
2021-07-19 17:02 John Kitchin
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='CAF-FPGMWgjHMkDvZeB5EP=C1LnGQAZCs9=+MikpgOmNu4t_OiQ@mail.gmail.com' \
--to=bdarcus@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=emm.charpentier@free.fr \
--cc=jkitchin@andrew.cmu.edu \
/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).