From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Roland Winkler" <winkler@gnu.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: Tue, 25 May 2021 00:04:38 +0200 [thread overview]
Message-ID: <878s43aivd.fsf@gnus.org> (raw)
In-Reply-To: <3816.41298.758059.24740@gargle.gargle.HOWL> (Roland Winkler's message of "Tue, 18 May 2021 14:00:56 -0500")
"Roland Winkler" <winkler@gnu.org> writes:
> I vaguely remember an old thread that started from the very question
> raised here and expanding on how asciification can be encapsulated
> in some generic piece of elisp code. But I cannot find it anymore
> and I do not know either whether this would be possible at all. I
> believe, everyone agrees on asciification of German umlaute like
>
> ä -> ae
>
> But beyond that, I do not know how to do this satisfactorily.
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"?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-05-24 22:04 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 [this message]
2021-05-26 18:56 ` Roland Winkler
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=878s43aivd.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=47455@debbugs.gnu.org \
--cc=be@mek.dtu.dk \
--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 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).