unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Roland Winkler" <winkler@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 47455@debbugs.gnu.org, Brian Elmegaard <be@mek.dtu.dk>
Subject: bug#47455: 27.1; bibtex mode - citation key generation - non-ascii characters
Date: Wed, 26 May 2021 13:56:53 -0500	[thread overview]
Message-ID: <39413.75034.396197.24750@gargle.gargle.HOWL> (raw)
In-Reply-To: <878s43aivd.fsf@gnus.org>

On Tue May 25 2021 Lars Ingebrigtsen wrote:
> And this gets even more difficult to deal with for non-Latin scripts.
> 
> So I'm not sure anything here can be done programmatically...  the
> command could output a warning?  "Probably invalid key"?

The warning is a good idea.  Actually, the warning should be issued
if there are non-ascii characters anywhere in a BibTeX key because
(oldfashioned) BibTeX will choke on those no matter where they
appear.  So I'll add a new element for the user variable
bibtex-entry-format for this.  Then users can enable these warnings
if they use oldfashioned BibTeX.  (Those who use modern variants of
BibTeX need not enable these warnings.)

I believe that the real problem here lies in the fact that many
publishers of scientific journals let you download citation records
for their journal articles.  When they offer not only BibTeX-formatted
records but other formats, too, the BibTeX records are often
malformed, decorated with non-ascii characters that BibTeX (and
LaTeX) cannot handle and other things.  I have been fooled a number
of times by "invisible" non-ascii characters.  So I will enable the
new option for myself!





  reply	other threads:[~2021-05-26 18:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-28 21:26 bug#47455: 27.1; bibtex mode - citation key generation - non-ascii characters Brian Elmegaard via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-18 16:05 ` Lars Ingebrigtsen
2021-05-18 19:00   ` Roland Winkler
2021-05-24 22:04     ` Lars Ingebrigtsen
2021-05-26 18:56       ` Roland Winkler [this message]
2021-05-28  7:17         ` Brian Elmegaard via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-30 21:39           ` Roland Winkler
2021-05-31  5:48             ` Lars Ingebrigtsen
2021-06-01  9:14           ` Arash Esbati
2021-06-01 14:37             ` Roland Winkler
2022-12-30  6:34               ` 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=39413.75034.396197.24750@gargle.gargle.HOWL \
    --to=winkler@gnu.org \
    --cc=47455@debbugs.gnu.org \
    --cc=be@mek.dtu.dk \
    --cc=larsi@gnus.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 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).