Bug#704527: biber: Character "(" not allowed in key although valid in BiBTeX
Control: reassign 704527 biber
Am 02.04.2013 um 14:55 teilte Harri Kiiskinen mit:
Hi Harri,
Long standing issue, I know.
> biber does not seem to accept the character "(" in a bibtex key. This
> is rather irritating, as the old bibtex did accept it along some
> other non-letter characters. This may of course be a conscious choice
> of the developers, but in any case it breaks the backwards
> compatibility of the databases (and for me, a lot of documents) and
> perhaps should be investigated. In older versions of biber there was
> an option to select a different type of parser, which in fact did
> circumvent the problem, but this option has obviously been removed.
>
A few years has gone, we are at biber 2.12 currently. Could you re-check
if the problem has been solved meanwhile? If not please provide a test
case. Thanks!
Hilmar
--
sigfault
#206401 http://counter.li.org
signature.asc
Description: OpenPGP digital signature
Bug#704527: biber: Character "(" not allowed in key although valid in BiBTeX
control: tag -1 wontfix upstream
Harri Kiiskinen writes:
> biber does not seem to accept the character "(" in a bibtex key. This
> is rather irritating, as the old bibtex did accept it along some other
> non-letter characters. This may of course be a conscious choice of the
> developers, but in any case it breaks the backwards compatibility of
> the databases (and for me, a lot of documents) and perhaps should be
> investigated. In older versions of biber there was an option to select
> a different type of parser, which in fact did circumvent the problem,
> but this option has obviously been removed.
I forwarded your request to the libbtparse maintainer [1]. Unfortunately
it looks like your problem will not be fixed in libbtparse. I don't
know it's worth persuing upstream with biber or not. Maybe we could at
least ask biber to document their (inherited) incompatibility?
[1]: https://rt.cpan.org/Ticket/Display.html?id=125914
Bug#704527: biber: Character "(" not allowed in key although valid in BiBTeX
> Hmm, I had a look at the repository and recently closed issues + open > issues, but did not find something. Indeed, I mis-remembered some issue emails, sorry for the work. Probably a good idea to open an issue at the github page? Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. +JAIST +TeX Live +Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#704527: biber: Character "(" not allowed in key although valid in BiBTeX
On 15.12.2017 20:57, Norbert Preining wrote: Hi Norbert, > I faintly remember some discussion on one of the recent biber issues > on github and a new version coming out that fixes that. > Hmm, I had a look at the repository and recently closed issues + open issues, but did not find something. The 2.10 beta at least still reports this as syntax error: hille@amd64-sid:~$ biber 704527 INFO - This is Biber 2.10 (beta) INFO - Logfile is '704527.blg' INFO - Reading '704527.bcf' INFO - Found 1 citekeys in bib section 0 INFO - Processing section 0 INFO - Looking for bibtex format file '704527.bib' for section 0 INFO - Reading ascii input as UTF-8 INFO - LaTeX decoding ... INFO - Found BibTeX data source '704527.bib' ERROR - BibTeX subsystem: /tmp/XiQzd7D7kf/704527.bib_11146.utf8, line 1, syntax error: found ")", expected "," INFO - ERRORS: 1 However I'm not sure if it is even the fault of biber. If you know more, let us know. Thanks! Hilmar -- http://www.hilmar-preusse.de.vu/ #206401 http://counter.li.org
Bug#704527: biber: Character "(" not allowed in key although valid in BiBTeX
On 15.12.2017 20:57, Norbert Preining wrote: Hi, > I faintly remember some discussion on one of the recent biber issues on > github and a new version coming out that fixes that. > > Sorry, not too much time to actually check as I am travelling. > Many thanks! At least the 2.9 recently uploaded does not solve the problem. Hilmar -- http://www.hilmar-preusse.de.vu/ #206401 http://counter.li.org
Bug#704527: biber: Character "(" not allowed in key although valid in BiBTeX
> defined syntax for this. In [1] I found the statement that "(" is an
I faintly remember some discussion on one of the recent biber issues on
github and a new version coming out that fixes that.
Sorry, not too much time to actually check as I am travelling.
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#704527: biber: Character "(" not allowed in key although valid in BiBTeX
reassign 704527 libbtparse1
tags 704527 + moreinfo
stop
On 02.04.2013 14:55, Harri Kiiskinen wrote:
Hi Harri,
> biber does not seem to accept the character "(" in a bibtex key.
> This is rather irritating, as the old bibtex did accept it along some
> other non-letter characters. This may of course be a conscious choice
> of the developers, but in any case it breaks the backwards
> compatibility of the databases (and for me, a lot of documents) and
> perhaps should be investigated. In older versions of biber there was
> an option to select a different type of parser, which in fact did
> circumvent the problem, but this option has obviously been removed.
>
> All the best,
>
Sorry, late response!
I tried to find some informations about this. The main statement (as
already written by Mark J. Nelson ): there is no real well
defined syntax for this. In [1] I found the statement that "(" is an
active character in biber, used to start an entry, and hence can't be
used in a key words. On the other hand I could replace the curly
delimiter braces in the bibtex file by "(" and bibtex still can process
the file. So I'd still vote for "regression".
[1] further describes how to use parentheses in aliases. Other matches
in the Internet suggest to replace the "()" by uncritical characters, in
[2] anybody provided python scripts to do so.
For now I reassign the issue to libbtparse1. Do you have an opinion for
this or a valid source to decide if we look at a bug or a missing
feature? Many thanks!
Hilmar
[1]
https://tex.stackexchange.com/questions/96454/using-bibtex-keys-containing-parentheses-with-biber
[2] https://github.com/JabRef/jabref/issues/1272
--
http://www.hilmar-preusse.de.vu/ #206401 http://counter.li.org
Bug#704527: biber: Character "(" not allowed in key although valid in BiBTeX
This bug should perhaps be reassigned to libbtparse1, since biber
currently defers to btparse on this matter. Unless biber would consider
changing its parsing back-end, it should probably be fixed (if at all)
in btparse.
From the btparse syntax documentation at
http://search.cpan.org/~gward/btparse-0.34/doc/bt_language.pod,
parentheses are purposely excluded from keys, but it's not clear if
that's due to a misunderstanding about whether they were allowed in
BibTeX. The documentation justifies why btparse removes '@', '\', and
'~' from the characters allowed in keys, even though BibTeX accepts
those three chars. But the docs claim that the following 10 characters
were already disallowed in BibTeX keys:
" # % ' ( ) , = { }
As you point out, this seems not to be true, since parentheses do work
in BibTeX. From my (non-expert) read of the PCCTS grammar under the
hood, it *should* be an easy fix: LPAREN as a semantically meaningful
element is only used in one very specific place in a BibTeX grammar, in
@comments, which shouldn't interfere with permitting parentheses in
entry keys. But I have not tried it.
Best,
Mark
--
Mark J. Nelson
IT University of Copenhagen
http://www.kmjn.org/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#704527: biber: Character "(" not allowed in key although valid in BiBTeX
Package: biber
Version: 0.9.9+release-1
Severity: normal
Dear Maintainer,
biber does not seem to accept the character "(" in a bibtex key. This is rather
irritating, as the old bibtex did accept it along some other non-letter
characters. This may of course be a conscious
choice of the developers, but in any case it breaks the backwards compatibility
of the databases (and for me, a lot of documents) and perhaps should be
investigated. In older versions of biber there
was an option to select a different type of parser, which in fact did
circumvent the problem, but this option has obviously been removed.
All the best,
Harri Kiiskinen
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages biber depends on:
ii libdata-compare-perl1.22-0.1
ii libdata-dump-perl 1.21-1
ii libdate-simple-perl 3.03.03-1+b3
ii libfile-slurp-unicode-perl 0.7.1-1
ii libipc-run3-perl0.045-1
ii liblist-allutils-perl 0.03-1
ii liblist-moreutils-perl 0.33-1+b1
ii liblog-log4perl-perl1.29-1
ii liblwp-protocol-https-perl 6.03-1
ii libreadonly-perl1.03-4
ii libregexp-common-perl 2011121001-1
ii libtext-bibtex-perl 0.63-1
ii libunicode-collate-perl 0.89-1
ii libwww-perl 6.04-1
ii libxml-libxml-simple-perl 0.91-1
ii libxml-libxslt-perl 1.77-1
ii libxml-writer-string-perl 0.1-1
ii perl5.14.2-20
ii perl-modules [libunicode-collate-perl] 5.14.2-20
Versions of packages biber recommends:
ii biblatex 1.7-1
ii libreadonly-xs-perl 1.04-2+b3
biber suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
