unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Arash Esbati <arash@gnu.org>
To: 47455@debbugs.gnu.org
Cc: larsi@gnus.org, winkler@gnu.org, be@mek.dtu.dk
Subject: bug#47455: 27.1; bibtex mode - citation key generation - non-ascii characters
Date: Tue, 01 Jun 2021 11:14:50 +0200	[thread overview]
Message-ID: <86mtsaeyk5.fsf@gnu.org> (raw)
In-Reply-To: <730b1644528547f78ea6910f882591d6@mek.dtu.dk> (Brian Elmegaard via's message of "Fri, 28 May 2021 07:17:10 +0000")

Brian Elmegaard via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs@gnu.org> writes:

> Thanks for looking into this.
> I understand your reasoning about this being an issue with the tools
> used.  In auctex I can also enter \newcommand{\ü}{u} without being
> warned that it will not work with latex.

It's not about LaTeX as the macro package, it's about the underlying
engine.  This example

    \documentclass[10pt]{article}
    \newcommand\ü{foo}
    \begin{document}
    \ü bar
    \end{document}

works when your run lualatex on it, but chokes with pdflatex.  The
reason is described in ltnews30.pdf:

    Improving Unicode handling in pdfTEX

    [...]  What is not possible when using an 8-bit engine such as
    pdfTEX is to use characters other than ascii letters as part of a
    command name. This is due to the fact that all other characters in
    such engines are not single character tokens, but in fact consist of
    a sequence of bytes and this is not supported in command names.

So yes, it about the tools used :-)

Best, Arash





  parent reply	other threads:[~2021-06-01  9:14 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
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 [this message]
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=86mtsaeyk5.fsf@gnu.org \
    --to=arash@gnu.org \
    --cc=47455@debbugs.gnu.org \
    --cc=be@mek.dtu.dk \
    --cc=larsi@gnus.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 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).