Re: [AUCTeX-devel] Typeset LaTeX files with non-ascii file name in TeXLive 2018

[Ikumi Keita]

Hi Colin,

>>>>> Colin Baxter <address@hidden> writes:

> I really do not like what I understand to be this suggestion. If users
> cannot put TeX codes in a command then extensive functionality is
> lost. The bar on non-ascii file names seems trivial to me - sorry.

Thanks for your comment. I made out another patch, attached with this
message, which continues to let the user to be able to put TeX codes on
the command line, with some drawbacks explained later.

In fact, even with my previous patch, it is possible to retain the
functionality to put TeX codes in a command line.  If you modify the
relavant entries in `TeX-command-list' (or add new entries) so that it
looks as
("TeX" "%(PDF)%(tex) %(file-line-error) %(extraopts) %`%S%(PDFout)%(mode)%'
 %t" ...
("LaTeX" "%`%l%(mode)%' \"\\detokenize\"{%t}" ...
, you can still use `TeX-command-extra-options' to put raw TeX codes.

The difference between my two patches are summarized below:
1. Previous patch
   Good points:
   - LaTeX format version banner is not discarded in the log file. [1]
   - First line parsing is not disabled. [2]
   - Bug#25276 is fixed. [3]
   Bad points:
   - Users cannot put TeX codes in a command line by default.
2. New patch
   Good points:
   - Users still can put TeX codes in a command line.
   Bad points:
   - LaTeX format version banner is discarded in the log file by default.
   - First line parsing is disabled by default.
   - Bug#25276 remains.

Both approaches fix the original problem about non-ascii file names, and
in both cases, the bad points are circumvented by customizing
`TeX-command-list'.  However, if `TeX-command-list' is customized, the
user have to edit the cusomization every time a new AUCTeX release
contains modification to the default value of the variable, in order to
incorporate that modification into one's customized value.
Colin, could you please compare the two situations?  I still prefer the
approach of the previous patch, but will honor your opinion if you are
still against it.

Best regards,
Ikumi Keita

[1] https://lists.gnu.org/archive/html/auctex/2018-05/msg00003.html
[2] https://lists.gnu.org/archive/html/auctex/2018-05/msg00004.html
[3] https://lists.gnu.org/archive/html/auctex/2018-05/msg00010.html

non-ascii-file-name-v3.gz
Description: Continue to use \input