From: Roland Winkler <winkler@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Arash Esbati <arash@gnu.org>, 69266-done@debbugs.gnu.org
Subject: bug#69266: 30.0.50; bibtex-parse-entry misreads escaped \}
Date: Thu, 02 Jan 2025 00:14:45 -0600 [thread overview]
Message-ID: <871pxlhhd6.fsf@gnu.org> (raw)
In-Reply-To: <877cirvyua.fsf@gnu.org> (Roland Winkler's message of "Mon, 26 Feb 2024 12:56:29 -0600")
On Mon, Feb 26 2024, Roland Winkler wrote:
> On Mon, Feb 26 2024, Ihor Radchenko wrote:
>> 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;
>
> "crossref" fields are already part of BibTeX. Do you say biblatex
> "crossref" fields go beyond what BibTeX "crossref" fields offer?
> Please be specific in a new bug report.
>
>> field aliases;
>
> Agreed, field aliases including customizable field aliases could be
> useful. Aliases for entries would probably be yet more useful.
> If I remember correctly, biblatex defines a bunch of entry types that
> are really just aliases for other entries.
>
>> and special key-value format like
>> AUTHOR = {given=Hans, family=Harman and given=Simon, prefix=de,
>> family=Beumont}
>
> If you submit a separate bug report, please include a description what a
> meaningful support could look like. As far as I know, emacs does not
> provide a good general scheme for filling a set of fields like "given",
> "prefix", and "family". I am not sure the above justifies to come up
> with a sophisticated scheme for that.
The discussion under the original bug report has drifted away from the
original topic. Part of the discussion has been addressed with
commit b26418694e8. For remaining issues please submit a separate
specific bug report.
Closing.
prev parent reply other threads:[~2025-01-02 6:14 UTC|newest]
Thread overview: 11+ 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
2024-02-26 18:56 ` Roland Winkler
2025-01-02 6:14 ` Roland Winkler [this message]
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=871pxlhhd6.fsf@gnu.org \
--to=winkler@gnu.org \
--cc=69266-done@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).