all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Stein <leo.stein@gmail.com>
To: Roland Winkler <winkler@gnu.org>
Cc: Leonard Lausen <leonard@lausen.nl>, 51621@debbugs.gnu.org
Subject: bug#51621: 29.0.50; bibtex.el biblatex "2.1.3 Non-standard Types" support
Date: Mon, 2 Dec 2024 11:23:31 -0600	[thread overview]
Message-ID: <CAE56pjF_zjiCZfKRK-7UdCj2G+YLmkn2xuUgc0eGOHUO=dufsg@mail.gmail.com> (raw)
In-Reply-To: <87mshekwo5.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2676 bytes --]

Dear Roland,

First of all, thanks for maintaining this very handy mode!

On Mon, Dec 2, 2024 at 8:05 AM Roland Winkler <winkler@gnu.org> wrote:

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


I really wish this was more permissive. Looking at a .bib file, we have no
way of knowing the biblio style that it's going to be set with. We also
have no way of knowing whether the user is going to parse it with bibtex or
biber.


>   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 still missing something... as far as I can tell, the "dialect" is just
controlling which entries are valid. Is that right? But this is not within
the purview of whether we use bibtex, or biber+biblatex. It depends on the
biblio style that the user wants to use for setting their bibliography.


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

I'm happy to hear that there will be future improvements. I sincerely
request that parsing of entries be made more permissive — not restricted to
a list of entry types, or relying on the user to make some customizations
[I think most users are not going to discover that it's possible
to customize this].


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

Again I don't understand why bibtex-mode is making a distinction. The
syntax of the .bib is identical whether the user wants to use bibtex or
biber+biblatex.

Best,
Leo

[-- Attachment #2: Type: text/html, Size: 3745 bytes --]

  reply	other threads:[~2024-12-02 17:23 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
2024-12-02 17:23   ` Leo Stein [this message]
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

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

  git send-email \
    --in-reply-to='CAE56pjF_zjiCZfKRK-7UdCj2G+YLmkn2xuUgc0eGOHUO=dufsg@mail.gmail.com' \
    --to=leo.stein@gmail.com \
    --cc=51621@debbugs.gnu.org \
    --cc=leonard@lausen.nl \
    --cc=winkler@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.