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 _______________________________________________ auctex mailing list [email protected] https://lists.gnu.org/mailman/listinfo/auctex
