From: Roland Winkler <winkler@gnu.org>
To: Arash Esbati <arash@gnu.org>
Cc: Ihor Radchenko <yantar92@posteo.net>, 69266@debbugs.gnu.org
Subject: bug#69266: 30.0.50; bibtex-parse-entry misreads escaped \}
Date: Sun, 25 Feb 2024 18:50:12 -0600 [thread overview]
Message-ID: <87edd0xd4r.fsf@gnu.org> (raw)
In-Reply-To: <m21q90cu26.fsf@macmutant.fritz.box> (Arash Esbati's message of "Sun, 25 Feb 2024 18:50:09 +0100")
On Sun, Feb 25 2024, Arash Esbati wrote:
> The following code doesn't throw an error for me with LaTeX2e
> <2023-11-01> patch level 1:
>
> \documentclass{article}
>
> \begin{document}
>
> \noindent \{x\}\\
> \textbraceleft x\textbraceright
>
> \end{document}
Indeed, "\{" must have become available as a command outside math mode
after I learned LaTeX many years ago. (I believe it is still correct to
say that from LaTeX's perspective "\{" is a macro that is very different
from escaping available in other programming languages.)
> 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.
next prev parent reply other threads:[~2024-02-26 0:50 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 [this message]
2024-02-26 14:42 ` Arash Esbati
2024-02-26 17:08 ` Ihor Radchenko
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edd0xd4r.fsf@gnu.org \
--to=winkler@gnu.org \
--cc=69266@debbugs.gnu.org \
--cc=arash@gnu.org \
--cc=yantar92@posteo.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).