unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Roland Winkler <winkler@gnu.org>
To: 51621@debbugs.gnu.org
Cc: Leo Stein <leo.stein@gmail.com>, Leonard Lausen <leonard@lausen.nl>
Subject: bug#51621: 29.0.50; bibtex.el biblatex "2.1.3 Non-standard Types" support
Date: Mon, 02 Dec 2024 08:05:14 -0600	[thread overview]
Message-ID: <87mshekwo5.fsf@gnu.org> (raw)
In-Reply-To: <87v91618i8.fsf@lausen.nl>

> I'm starting to think that the "dialect" design within bibtex.el was
> confused about bibtex vs. biblatex (this is pretty confusing, as we
> can see here: https://tex.stackexchange.com/q/25701/34063). However,
> I'm not sure what is the correct solution. At the very least,
> bibtex.el should be more permissive about what entry types get parsed
> by bibtex-parse-entry.

The range of "acceptable" entry types needs to be compatible with the
BibTeX style files that one wants to use.  Certainly, these style files
can be modified to handle any entry types you like.  But I am not sure
it makes sense to extend the defaults of bibtex.el beyond the defaults
defined by BibTeX and / or biblatex.  If you want to use the full range
of entry types defined by biblatex, you may be served better by making
biblatex your default dialect of bibtex-mode.  (I find it useful if
bibtex-mode keeps track of the entry types known to a dialect.)

I am currently working on a patch for bibtex-mode that will make it
easier for users to customize the entry types known by a dialect,
including the possibility to define aliases for entry types.  This patch
should be installed on master in a few weeks.  (I want to test it
first.)

PS: My reading of the above thread on stackexchange is that it will not
make everyone happy if the distinction between old BibTeX and new
biblatex gets blurred by bibtex-mode.





  parent reply	other threads:[~2024-12-02 14:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05 23:35 bug#51621: 29.0.50; bibtex.el biblatex "2.1.3 Non-standard Types" support Leonard Lausen
2021-11-07  3:37 ` Roland Winkler
2024-12-01  4:33 ` Leo Stein
2024-12-02 14:05 ` Roland Winkler [this message]
2024-12-02 17:23   ` Leo Stein
2024-12-03 20:37     ` Roland Winkler
2024-12-03 21:12       ` Leo Stein

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mshekwo5.fsf@gnu.org \
    --to=winkler@gnu.org \
    --cc=51621@debbugs.gnu.org \
    --cc=leo.stein@gmail.com \
    --cc=leonard@lausen.nl \
    /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.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).