Le 21/05/2018 à 11:34, jfbu a écrit :
Le 21/05/2018 à 11:04, jfbu a écrit :
If AUCTeX provides a user-interface for extra TeX commands on
command-line, via some variable, couldn't it check for that
variable being or not nil. If nil, do not use \input, if not
nil, use the \input with whatever extra measures are needed
from the fact that any command will be executed after the format
is loaded, hence the non-ascii characters assumed to be utf-8
and their first byte is active.
Ah sorry for the confusion in this paragraph.
In fact, the utf-8 first bytes are active in both cases,
but in the case of
pdflatex filename
they have a temporary definition based on \string
and the thing works
For reference on this, these links
http://tug.org/pipermail/tex-live/2018-May/041669.html
https://github.com/latex3/latex2e/commit/93b375e40e3dbfd57093e5b527be1d357a942a99
indirectly explain it, because there was a problem on Windows
that utf-8 filenames are presented to the binary in another encoding.
The commit above contains modified definitions for the
LaTeX \UTFviii@.... macros, but indirectly it does illustrate
that the mechanism is in place already in
pdflatex filename
situation.
The difference with
pdflatex "\input" filename
is that \input is processed at a later time and the LaTeX
\UFTviii@... macros have by then another meaning.
I think.
Best
Jean-François
Hi Keita, (sorry for having mixed-up firstname and lastname)
A.
In TeX-expand-list-builtin, there is in PDFout a possibility
if variable TeX-DVI-via-PDFTeX is t that the command line will
do \pdfoutput=0. This is a situation which would then necessitate
usage of \input, because it is either \commands or filename.
However that possibility looks very obsolete because it is
long since that "latex" command is aliased to pdfetex in a
way which sets \pdfoutput without having to do it manually.
B.
About this in the patch under discussion
+ ;; Since TeXLive 2018, the default encoding for LaTeX files has been
+ ;; changed to UTF-8 if used with classic TeX or pdfTeX. I.e.,
+ ;; \usepackage[utf8]{inputenc} is enabled by default in (pdf)latex.
+ ;; c.f. LaTeX News issue 28
+ ;; Due to this change, \detokenize is required to recognize non
+ ;; ascii characters in the file name.
The exact explanation would be that this is required in case the
\input method of executing the file is used. It is not required
in the case of "pdflatex filename" invocation, not because the non-ascii
letters are not handled in a special way
but because they are handled in a self-innocenting way
as long as \everyjob has not been executed after which they acquire
their proper \usepackage[utf8]{inputenc} form.
Best
Jean-François
_______________________________________________
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
