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: Sat, 24 Feb 2024 12:19:22 +0000 [thread overview]
Message-ID: <8734tixdf9.fsf@localhost> (raw)
In-Reply-To: <87a5nr9p8f.fsf@gnu.org>
Roland Winkler <winkler@gnu.org> writes:
> Ihor Radchenko <yantar92@posteo.net> writes:
>> According to https://www.bibtex.org/SpecialSymbols/, characters that
>> conflict with Bibtex format description can be \-escaped.
>
> I believe the above webpage is incorrect. If I put something like \}
> into a BibTeX field, BibTeX complains about unbalanced braces.
> This is with BibTeX, Version 0.99d (TeX Live 2022/Debian).
> The parsing algoritm used by BibTeX is very simple. Generally,
> BibTeX fields should contain valid LaTeX code. So something
> like
> title = "$\}$tex",
>
> should work with BibTeX, but it gives the same error message
> "unbalanced braces".
I am wondering if there exists a full Bibtex format description
somewhere. I can see some hints scattered over documentation in
https://ctan.org/pkg/bibtex, but nothing is complete.
--
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-24 12:19 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 [this message]
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
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=8734tixdf9.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.