From: Ihor Radchenko <yantar92@posteo.net>
To: Roland Winkler <winkler@gnu.org>
Cc: Arash Esbati <arash@gnu.org>, 69266@debbugs.gnu.org
Subject: bug#69266: 30.0.50; bibtex-parse-entry misreads escaped \}
Date: Mon, 26 Feb 2024 17:08:31 +0000 [thread overview]
Message-ID: <87v86bb1bk.fsf@localhost> (raw)
In-Reply-To: <87edd0xd4r.fsf@gnu.org>
Roland Winkler <winkler@gnu.org> writes:
>> Would you reconsider this if Biber handles \} correctly? I didn't
>> test it, though.
>
> I am happy to take advice from more advanced biber / biblatex users.
> For the fun of it, I just created my first LaTeX document using biber /
> biblatex. That worked fine with balanced braces. But it choked with a
> biber error message when a biblatex field contained a single "\{".
>
> Biber uses btparse to parse BibTeX files. The BibTeX data language, as
> recognized by btparse is explained here
>
> https://metacpan.org/dist/Text-BibTeX/view/btparse/doc/bt_language.pod
>
> My reading of this document is that btparse does no take steps to deal
> with "escaped braces" inside a field.
Well. btparse does not really try to implement bibtex syntax accurately.
The docs just say that there is no formal description other than the
code and give up, pointing that some more accurate parsers do exist, but
btparse is not one of these more accurate parsers.
That said, since bibtex itself chokes on \}, this bug report is notabug.
Also, talking about biblatex, I do note that
https://ctan.org/pkg/biblatex has a more detailed description of the
syntax with notable differences from bibtex. For example, biblatex
allows "crossref" field that defines entry inheritance; field aliases;
and special key-value format like
AUTHOR = {given=Hans, family=Harman and given=Simon, prefix=de, family=Beumont}
See https://ctan.org/pkg/biblatex
It would be nice to have those supported. I may open another bug report
if you think that this idea is worth tracking.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-02-26 17:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 9:14 bug#69266: 30.0.50; bibtex-parse-entry misreads escaped \} Ihor Radchenko
2024-02-23 12:07 ` Arash Esbati
2024-02-23 15:25 ` Roland Winkler
2024-02-24 12:19 ` Ihor Radchenko
2024-02-24 16:05 ` Roland Winkler
2024-02-25 17:50 ` Arash Esbati
2024-02-26 0:50 ` Roland Winkler
2024-02-26 14:42 ` Arash Esbati
2024-02-26 17:08 ` Ihor Radchenko [this message]
2024-02-26 18:56 ` Roland Winkler
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=87v86bb1bk.fsf@localhost \
--to=yantar92@posteo.net \
--cc=69266@debbugs.gnu.org \
--cc=arash@gnu.org \
--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.