From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Roland Winkler Newsgroups: gmane.emacs.bugs Subject: bug#57246: biblatex don't recognize video type entry Date: Wed, 17 Aug 2022 17:55:49 -0500 Message-ID: <87tu6acwei.fsf@gnu.org> References: <87v8qrglny.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16150"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Cletip Cletip , 57246@debbugs.gnu.org To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Aug 18 00:56:11 2022 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 1oORxK-00043A-HR for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 18 Aug 2022 00:56:10 +0200 Original-Received: from localhost ([::1]:33434 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oORxJ-0000zp-18 for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 17 Aug 2022 18:56:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54272) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oORxC-0000z6-J5 for bug-gnu-emacs@gnu.org; Wed, 17 Aug 2022 18:56:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:35286) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oORxC-0006VH-As for bug-gnu-emacs@gnu.org; Wed, 17 Aug 2022 18:56:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oORxC-0008Pd-2I for bug-gnu-emacs@gnu.org; Wed, 17 Aug 2022 18:56:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Roland Winkler Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 17 Aug 2022 22:56:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 57246 X-GNU-PR-Package: emacs Original-Received: via spool by 57246-submit@debbugs.gnu.org id=B57246.166077696032329 (code B ref 57246); Wed, 17 Aug 2022 22:56:02 +0000 Original-Received: (at 57246) by debbugs.gnu.org; 17 Aug 2022 22:56:00 +0000 Original-Received: from localhost ([127.0.0.1]:53268 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oORxA-0008PN-14 for submit@debbugs.gnu.org; Wed, 17 Aug 2022 18:56:00 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:33820) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oORx7-0008P9-Ie for 57246@debbugs.gnu.org; Wed, 17 Aug 2022 18:55:58 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:51660) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oORx2-0006UW-4L; Wed, 17 Aug 2022 18:55:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:In-Reply-To:Date:References:Subject:To: From; bh=VmD54XiL4y1xvpsyBQy+7QWMvuv8L3tqtQ3HIsdTgwk=; b=AMIoD9J1aK/ZxqEj/oo4 Jow34pEI3PmnNajnrA6GgC2axRkXwLAa76keyrIq4UTfAuJdSs9wTLDZm7EhmXvN20hz5/7DzWJI5 LocmGbmDw8ge1/R60uJj1syZWJg67JsD1j4q4LAYMqp0VpqhOk8Niwp9lkqjt+QSwuQGKpmRsgu0h iSGtRFQtH0rYV1vlEcfGSmFAPm2zxRN+I8oy1GKr8DBNGcUmgetT7MZsvkFW8jH6qCT2cFYeI6zU2 aOJ2/ICw59MxRkMr6VgMZOZliqusRViDU+Iq1NHiEZsWlglsCLQTAEr+TDHapqeLtNXtW+VxHdp83 PXnocsUb92/Ycw==; Original-Received: from [2600:1700:5650:f790::22] (port=47238 helo=regnitz) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oORx1-0008A6-SN; Wed, 17 Aug 2022 18:55:51 -0400 In-Reply-To: <87v8qrglny.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 17 Aug 2022 13:21:53 +0200") 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" Xref: news.gmane.io gmane.emacs.bugs:240116 Archived-At: On Wed, Aug 17 2022, Lars Ingebrigtsen wrote: > Cletip Cletip writes: > >> It's all in the object: biblatex does not recognize inputs of type "video". >> I think that the bibtex-biblatex-entry-alist variable (and maybe >> bibtex-biblatex-field-alist) should be modified > > Perhaps Roland has some comments here; added to the CCs. I believe these are non-standard biblatex entries with incomplete biblatex support. In Emacs BibTeX mode the problem is here that all biblatex entry types are defined via the rather "big" user variable bibtex-biblatex-entry-alist. So the idea is that users can customize this variable and define additional entry types. However, this is not a very practical strategy. From a technical perspective, there is still bug#53606. Also, as biblatex evolves, the default value of bibtex-biblatex-entry-alist is continuously updated with each release of Emacs. (Usually this refers to small changes concerning biblatex entry types that are already defined via this variable.) However, if a user customizes this variable in whatever way, she will miss the updated default value when the next release of emacs is shipped. I believe, these problems are not specific to BibTeX mode. There are several "big" user variables in Auctex where I am splicing my custom elements into an alist instead of using the customize machinery. This is not a very user-friendly approach. Often such "big" user variables are alists. Sometimes I have been wondering whether the customize machinery could provide special support for alists that allows one to modify or add individual cons cells without touching other cells that are part of the default value. Then if a new release of emacs uses updated values for such user variables, there are less opportunities for how this may collide with individual customizations. Would that be useful? In the present context, a simpler strategy would be to define a new user variable bibtex-biblatex-extra-entry-alist that complements / overrides the defaults in bibtex-biblatex-entry-alist.