[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [AUCTeX] files with non-ascii characters and LaTeX as in TeXLive 201

From: Ikumi Keita
Subject: Re: [AUCTeX] files with non-ascii characters and LaTeX as in TeXLive 2018
Date: Fri, 18 May 2018 15:36:16 +0900

Hi Jean, thank you very much for clarifying!

First of all, my thought about the behavior of \message was wrong.  I
> The output of \message{...} also changed in TeXLive 2018.  If
> non-ascii characters are in \message{...}, they are output in
> tokenized form by default in TL 2018.
before, but it didn't change in fact.  I'm sorry about that.  The dummy
document I used for test lacked \usepackage[utf8]{inputenc}, so it
looked to me as if the behavior had changed between TL 2017 and 2018.

And after reading carefully texdoc ltnews again, I noticed that it
states that "the default encoding for LaTeX files has been changed to
UTF-8 if used with classic TeX or pdfTeX" and realized latex variants
includeing xelatex, lualatex (and lambda, lamed?) were not affected by
the TL 2018 change.

>>>>> jfbu <address@hidden> writes:

> Perhaps you can use this mouthful

> pdflatex  -file-line-error   -interaction=nonstopmode 
> "\begingroup\ifdefined\UseRawInputEncoding\UseRawInputEncoding\fi\edef\x{\noexpand\input{\string#éàè\string~\string#.tex}}\expandafter\endgroup\x"
> I am indicating this if there exists context where using "\input" is needed,
> because preferred form is not use "\input" at all.

In fact `TeX-quote-filename' is used only within \message{}, so we don't
have to consider the command line argument as long as my patches are
concerned.  But thanks anyway.  (And your code above would be useful for
anyone else who prefers other approach than my patches.)

> Regarding your problem with \message{...}. Perhaps
> \unexpanded will help you, as this shows (with April 2018 LaTeX)

> \documentclass{article}

> \begin{document}
> \message{éàù}% gives about 72 macros ....

> \message{\unexpanded{éàù}}% just displays éàù

> \message{\unexpanded{#}}% does not help the doubling... \string# helps
> \end{document}

Thanks for suggestion.  It seems that \unexpanded and \detokenize have
basically the same effect within \message, but I suppose \unexpanded is
better for some reason, isn't it?

Anyway, `TeX-quote-filename' has been long since incompatible with
\usepackage[utf8]{inputenc} if file name contains non ascii characters,
even before TL 2018.

> On my AUCTeX i have long since modified the "tex" invocation
> to be alias for "etex" because I need e-TeX daily even with Plain.

> But the "tex" can't be modified officially because it is Knuth tex.

I see.  Thanks.

> - I have absolutely no idea about Japanese platex/uplatex

It is known that pLaTeX and upLaTeX are also subject to the change about
default UTF-8 in TL 2018.  (discussed in .)

>> (a) Should we treat `doctex-mode' in the same way as `latex-mode' in
>> this case?  I'm not sure since I don't know docTeX.

> doctex mode is only an auctex mode related to the ltxdoc document
> class (or scrdoc) which incorporates doc package

> as such it is but slight variation of latex so yes it should be
> handled like latex-mode

Thanks to this instruction, I managed to make out a revised patch, which
is attached with this message.  I hope it satisfies those who are
interested in this topic.

> (I don't think doctex-mode has special facilities to emulate
> docstrip behaviour for extracting files, if it did some other problems
> may arise, for example I use doctex-mode sometimes for packages
> working with etex, not needing latex)

I'm not sure, but I suppose that would be a minor issue hopefully and
could be ignored at least for the moment.

Best regards,
Ikumi Keita

Attachment: non-ascii-file-name-v2.gz
Description: revised patch

reply via email to

[Prev in Thread] Current Thread [Next in Thread]