emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "András Simonyi" <andras.simonyi@gmail.com>
To: Julien Chastang <julien.c.chastang@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-cite-insert does not like @conference [9.5.2 (release_9.5.2 @ ~/.emacs.d/git/org-mode/lisp/)]
Date: Sat, 1 Jan 2022 17:23:46 +0100	[thread overview]
Message-ID: <CAOWRwxAk-B8bqFry9r6ibBi-5L29yrCuhHxhjCRmaKLwhsuHcA@mail.gmail.com> (raw)
In-Reply-To: <CALDHLo3TmoJ-wwCXsz8cLZ1Pzda29iC2=8tmYoFyQcsTbP1hgQ@mail.gmail.com>

Dear All,

On Sat, 1 Jan 2022 at 14:53, Julien Chastang
<julien.c.chastang@gmail.com> wrote:

> I have been experimenting with org-cite. I noticed that I can insert (org-cite-insert) all bibtex types *except* for @conference. [...]
> yet I believe @conference is a valid bibtex type. I noticed that org-bibtex-types has an empty description for the conference type, but I don't know if that has anything to do with it. I hope I have not missed anything obvious.

it seems that 'conference' is indeed a valid BibTeX entry type, but is
only an alias of 'inproceedings' and was included for some (nowadays
obscure?) compatibility reasons, while biblatex doesn't support it at
Consequently, you can simply use 'inproceedings' instead. If this is
not an option, then you can force org-cite to parse a bibliography as
a (strict) BibTeX bibliography instead of the default biblatex parsing
by using the 'bibtex' extension in the file's name, this should cause
'conference' entries to be treated as valid.

best wishes,

      reply	other threads:[~2022-01-01 16:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-31 18:23 [BUG] org-cite-insert does not like @conference [9.5.2 (release_9.5.2 @ ~/.emacs.d/git/org-mode/lisp/)] Julien Chastang
2022-01-01 16:23 ` András Simonyi [this message]

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=CAOWRwxAk-B8bqFry9r6ibBi-5L29yrCuhHxhjCRmaKLwhsuHcA@mail.gmail.com \
    --to=andras.simonyi@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=julien.c.chastang@gmail.com \


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