From: Ihor Radchenko <yantar92@gmail.com>
To: 57712@debbugs.gnu.org
Subject: bug#57712: 29.0.50; bibtex.el: Should `bibtex-parse-entry' handle curly braces inside fields?
Date: Sat, 10 Sep 2022 12:32:57 +0800 [thread overview]
Message-ID: <87k06b26iu.fsf@localhost> (raw)
Hello,
Org mode is relying upon bibtex.el to parse BibTeX bibliographies.
Recently, we have got a bug report where curly braces are used inside
title field:
https://orgmode.org/list/CAF+0kSg8O3RQBG1wXoHjMEHwnGFz0gaDkTTSGv+ZaOt4d4myCA@mail.gmail.com
@InCollection{Geyer2011,
author = {Geyer, Charles J},
title = {{Introduction to Markov Chain Monte Carlo}},
^ ^
year = 2011,
booktitle = {{Handbook of Markov Chain Monte Carlo}},
editor = {Brooks, Steve and Gelman, Andrew and Jones, Galin and Meng,
Xiao-Li},
publisher = {CRC press},
pages = 45,
}
The curly braces inside fields are a part of BibTeX specification:
http://www.bibtex.org/SpecialSymbols/
Yet, bibtex-parse-entry simply ignores all the curly braces inside the
field and returns the field as is:
(("=type=" . "InCollection")
... ("title" . "{Introduction to Mark\\.{o}v Chain Monte Carlo}") ...)
The same goes for the \.{o} special symbol.
It would be useful if bibtex-parse-entry could process the escapes when,
say, its first optional argument CONTENT is set to 'parse.
Would it be possible?
--
Ihor Radchenko,
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 reply other threads:[~2022-09-10 4:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-10 4:32 Ihor Radchenko [this message]
2022-09-10 4:39 ` bug#57712: 29.0.50; bibtex.el: Should `bibtex-parse-entry' handle curly braces inside fields? Lars Ingebrigtsen
2022-09-10 16:07 ` Roland Winkler
2022-09-11 5:11 ` Roland Winkler
2022-09-12 5:20 ` Ihor Radchenko
2022-09-12 13:50 ` Roland Winkler
2022-09-13 2:34 ` Ihor Radchenko
2022-09-13 4:08 ` Roland Winkler
2022-09-14 2:07 ` Ihor Radchenko
2022-09-14 17:02 ` Roland Winkler
2022-12-30 6:39 ` Roland Winkler
2022-09-12 5:06 ` Ihor Radchenko
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=87k06b26iu.fsf@localhost \
--to=yantar92@gmail.com \
--cc=57712@debbugs.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.