From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Leo Stein Newsgroups: gmane.emacs.bugs 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 Message-ID: References: <87mshekwo5.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000bc8dde06284ccff0" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4375"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Leonard Lausen , 51621@debbugs.gnu.org To: Roland Winkler Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Dec 02 18:25:45 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tIAB7-0000z5-6H for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 02 Dec 2024 18:25:45 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tIAAr-0000Ji-1D; Mon, 02 Dec 2024 12:25:30 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tIAAU-0008Vr-V2 for bug-gnu-emacs@gnu.org; Mon, 02 Dec 2024 12:25:07 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1tIAAQ-00004q-Sz for bug-gnu-emacs@gnu.org; Mon, 02 Dec 2024 12:25:04 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=Date:From:In-Reply-To:References:MIME-Version:To:Subject; bh=7r04ujBlVHjJI6xuSn4LKCXtYdU24FRg2fFhRipzZI8=; b=Y57AFjcR5PW2m2srgyuLrOrZOy6IWrYGMjhxEcAS0TNCNnRb5UL7asuHgTmHe//YP+5/MeznCfZStnN5EowZ0xlY69teZqb64KVLvriWybxtcuH6PV+UO2RTC89F0LJyeQA4HzLoVTXJp2zRzpDrp7y2HCJVRtDCmT8/4h2AWQJHnSiRrJ5uULCyN0BhqQzxkUxrxb26PAkLHgjCRTfTzG1Gn7ch+VqZlZtLgA9JG7Jbptc0eVoD3Fcq+sqigjmm0a7Yl2mUH2auEI/x5zN7fTxQu6jhsmLSUT75sDB/YaFwcA/rmBn4OmuQ67G1afY26p2KNL3ZsQTiaNx/qP1nuw==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1tIAAQ-0004kv-EH for bug-gnu-emacs@gnu.org; Mon, 02 Dec 2024 12:25:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Leo Stein Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 02 Dec 2024 17:25:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 51621 X-GNU-PR-Package: emacs Original-Received: via spool by 51621-submit@debbugs.gnu.org id=B51621.173316029318250 (code B ref 51621); Mon, 02 Dec 2024 17:25:02 +0000 Original-Received: (at 51621) by debbugs.gnu.org; 2 Dec 2024 17:24:53 +0000 Original-Received: from localhost ([127.0.0.1]:56423 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tIAAG-0004kF-9a for submit@debbugs.gnu.org; Mon, 02 Dec 2024 12:24:52 -0500 Original-Received: from mail-yb1-f176.google.com ([209.85.219.176]:42288) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tIAAC-0004k5-QM for 51621@debbugs.gnu.org; Mon, 02 Dec 2024 12:24:49 -0500 Original-Received: by mail-yb1-f176.google.com with SMTP id 3f1490d57ef6-e39779a268bso3276439276.1 for <51621@debbugs.gnu.org>; Mon, 02 Dec 2024 09:24:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1733160228; x=1733765028; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=7r04ujBlVHjJI6xuSn4LKCXtYdU24FRg2fFhRipzZI8=; b=kp7oT9+L9Ej0sigjZvwToe8lTkGslzLg92mpekBYmZTjVWq86cSF6eb8d0QvwUDTM8 PWa4HEJGS7Jwu88DwRV4aejKwPZ4J6kYP3sxP14MSjo4u5y9W77mSuTY6auyQGfvKR+3 Rb/e+CHIJvQGDiA/x+HiFEUEEC/4BdQHzmzHs8thzh+wPH7tNUe2KzKFEVlFqV/ht5mr 66epqL97sg3im37cBW3fU9D2tIik+PAf60xcZ9SR81k4nO46B0bbrWb2lr7MF/KNjSWu 8X9FzmoM5mCuIMwfSSMMTjaJ0ABGFGFZKCbs+BgN+5Fy7n6+7uZqHdzYUJIBzM8JB7F7 lzxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733160228; x=1733765028; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=7r04ujBlVHjJI6xuSn4LKCXtYdU24FRg2fFhRipzZI8=; b=Yv8wwGtUrWa4250bxQ7ntLnXzgXKd9IG6bOFtzxSdydLRIjzrvJ4JwMFbAfWFOLQXk YloBm9WXSH24utj+zaUC/5UjoEePHJJVFmHjQr1F3T20vfmRR5I3SpxXT+/ZGQCl2hMO qmwTood0jTutDbUvKwDoyhpgc37tYmTHzCPZeIWGCya8rpBxZqFJnfsrwdcvYQKUP1M8 of71y3pbsnyaNPxoxTm+flESjMitsfTKG5BhUCN6keMh+fJBLjsJLa6fZQBKLejTZ72/ j9lMMCpThIA5ayKktVvlfAYWUklpk70S9gOp+KPKPNFbt5qtulriHGUQeOTJqY04L1ab 1/8w== X-Gm-Message-State: AOJu0Yx6pyIg0MvZHK16iTf5P1dgnEKYXnI26laMr7jFZmdpo6f0ttRO E0HCvOazyCKG4frwDdLEST6fqcR9+IHV8cS6RN5G61hNfg7bJQE+WfBB+TYWxUa/COhJBy2hKEm 2oznk+RopO1KbJ/Lyk2h6KgQl/fs= X-Gm-Gg: ASbGncsPS3HpnLIpnbx9jETdii5JDyEqqWH5pWvRKKqtTqfaYMd+jXIedKYBSGOOZym 8+GPUvihm89j5bkYqcF3BIPJxGI0uvyM4+DZtKX4XQKBOqJ8= X-Google-Smtp-Source: AGHT+IE9wCBzHGVZ1TQBWOq6F889MhK+Dp603Y1edr94hegIcuumf62HnGJ3yeXwjoU3PAAbydEXAtIv4trTXZKz0Bc= X-Received: by 2002:a25:7449:0:b0:e38:7d21:3b53 with SMTP id 3f1490d57ef6-e3971a1ad60mr18230223276.22.1733160228128; Mon, 02 Dec 2024 09:23:48 -0800 (PST) In-Reply-To: <87mshekwo5.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:296341 Archived-At: --000000000000bc8dde06284ccff0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Dear Roland, First of all, thanks for maintaining this very handy mode! On Mon, Dec 2, 2024 at 8:05=E2=80=AFAM Roland Winkler wro= te: > > 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 =E2=80=94 not restr= icted 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 --000000000000bc8dde06284ccff0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear Roland,

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

On Mon, Dec 2, 2024 = at 8:05=E2=80=AFAM Roland Winkler <wi= nkler@gnu.org> wrote:
> I'm starting to think that the "dialect" de= sign 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<= br> > by bibtex-parse-entry.

The range of "acceptable" entry types needs to be compatible with= the
BibTeX style files that one wants to use.=C2=A0 Certainly, these style file= s
can be modified to handle any entry types you like.=C2=A0 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 real= ly 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 bibe= r.
=C2=A0
= =C2=A0 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.=C2=A0 (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 te= ll, the "dialect" is just controlling which entries are valid. Is= that right? But this is not within the purview of whether we use bibtex, o= r biber+biblatex. It depends on the biblio style that the user wants to use= for setting their bibliography.
=C2=A0

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.=C2=A0 This pat= ch
should be installed on master in a few weeks.=C2=A0 (I want to test it
first.)

I'm happy to hear that ther= e will be future improvements. I sincerely request that parsing of entries = be made more permissive =E2=80=94 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=C2=A0customize this].
=
=C2=A0

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.

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

Best,
Leo
=C2=A0
--000000000000bc8dde06284ccff0--