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

[Ikumi Keita]

> Ikumi Keita  writes:

>> I am not really sure I understand the implications of your change. Would
>> it apply for all sort of latex documents or such with non ascii file names?

> All sort of documents processed with standard (pdf)latex without e-TeX
> extension.  LaTeX variants such as xelatex and lualatex are not
> affected.

More precisely,
- With respect to preview-latex:
  All sort of documents
- With respect to region compilation:
  Documents with non-ascii file names only

Best,
Ikumi Keita

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

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

[Ikumi Keita]

Hi Uwe,

> Uwe Brauer  writes:
> Again this is just for some particular binaries or in general? I am
> still with TL 2017.

> If it is a breakdown  in general of that feature I am _against_ it.

> Region compilation is a feature I rely on very much.

> But maybe I misunderstood the implication of your proposed changes.

  You are not affected because you use TeXLive 2017.  As I wrote
>> - (Pdf)latex binaries without e-TeX extension have the following two
>> limitations:
, the restrictions are limited to only (pdf)latex binaries _without_
e-TeX extension.
  Such binaries only exist in very old TeX distributions, at least for
TeXLive.
c.f. https://lists.gnu.org/archive/html/auctex/2018-05/msg00013.html
I know little about MikTeX, but I expect the situation is similar.

> I am not really sure I understand the implications of your change. Would
> it apply for all sort of latex documents or such with non ascii file names?

All sort of documents processed with standard (pdf)latex without e-TeX
extension.  LaTeX variants such as xelatex and lualatex are not
affected.

Regards,
Ikumi Keita

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

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

[Colin Baxter]

> Ikumi Keita  writes:

> Hi developpers, I'd like to commit a change proposed in
> https://lists.gnu.org/archive/html/auctex/2018-05/msg00014.html in
> order to resolve problems addressed in
> https://lists.gnu.org/archive/html/auctex/2018-05/msg3.html
> https://lists.gnu.org/archive/html/auctex/2018-05/msg4.html .
> Are there anyone who doesn't agree with this?

> As explained in ealier messages, this patch introduces some
> incompatibilities: - Users cannot put raw TeX codes in the command
> line like latex -interaction=nonstopmode \SOME_CODE \input
> FILENAME via setting `TeX-command-extra-options' anymore, as long
> as the default `TeX-command-list' is used.  - (Pdf)latex binaries
> without e-TeX extension have the following two limitations:
> 1. Preview-latex does not work.  (This can be circumvented by
> customizing `preview-LaTeX-command' and
> `preview-undump-replacements' to cancel the change by my patch,
> though) 2. Region compilation (C-c C-r, C-c C-e etc.) does not
> work.  I.e., such binaries can only use C-c C-c (and C-c C-a) to
> typeset the latex documents.  If you consider that these
> incompatibilities are not acceptable, please express your opinion.
> I would be ready to discuss about this.

> If no objection, I'll commit the change in a few days.  Adding
> document changes and regression tests will follow later.

> Best regards, Ikumi Keita

> P.S.  I tested the patch with MikTeX briefly, and encountered no
> errors.


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.

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

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

[Uwe Brauer]

>>> "Ikumi" == Ikumi Keita  writes:
Hi,


   > Hi developpers,
   > I'd like to commit a change proposed in
   > https://lists.gnu.org/archive/html/auctex/2018-05/msg00014.html
   > in order to resolve problems addressed in
   > https://lists.gnu.org/archive/html/auctex/2018-05/msg3.html
   > https://lists.gnu.org/archive/html/auctex/2018-05/msg4.html
   > .  Are there anyone who doesn't agree with this?

I am not really a developer (besides from trivial style files
contribution), but I am a very heavy auctex user on a daily base.
I am also interested in the issue of non ASCII file names (hebrew)

I am not really sure I understand the implications of your change. Would
it apply for all sort of latex documents or such with non ascii file names?


   > As explained in ealier messages, this patch introduces some
   > incompatibilities:
   > - Users cannot put raw TeX codes in the command line like
   >latex -interaction=nonstopmode \SOME_CODE \input FILENAME
   >   via setting `TeX-command-extra-options' anymore, as long as the
   >   default `TeX-command-list' is used.
   > - (Pdf)latex binaries without e-TeX extension have the following two
   >   limitations:
   >   1. Preview-latex does not work.  (This can be circumvented by
   >  customizing `preview-LaTeX-command' and
   >  `preview-undump-replacements' to cancel the change by my patch,
   >  though)

Oops that is a heavy one. But if it can be circumvented.
   >   2. Region compilation (C-c C-r, C-c C-e etc.) does not work.

Again this is just for some particular binaries or in general? I am
still with TL 2017.


If it is a breakdown  in general of that feature I am _against_ it.

Region compilation is a feature I rely on very much.

But maybe I misunderstood the implication of your proposed changes.


Uwe Brauer 


smime.p7s
Description: S/MIME cryptographic signature
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

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

[Ikumi Keita]

Hi developpers,

I'd like to commit a change proposed in
https://lists.gnu.org/archive/html/auctex/2018-05/msg00014.html
in order to resolve problems addressed in
https://lists.gnu.org/archive/html/auctex/2018-05/msg3.html
https://lists.gnu.org/archive/html/auctex/2018-05/msg4.html
.  Are there anyone who doesn't agree with this?

As explained in ealier messages, this patch introduces some
incompatibilities:
- Users cannot put raw TeX codes in the command line like
latex -interaction=nonstopmode \SOME_CODE \input FILENAME
  via setting `TeX-command-extra-options' anymore, as long as the
  default `TeX-command-list' is used.
- (Pdf)latex binaries without e-TeX extension have the following two
  limitations:
  1. Preview-latex does not work.  (This can be circumvented by
 customizing `preview-LaTeX-command' and
 `preview-undump-replacements' to cancel the change by my patch,
 though)
  2. Region compilation (C-c C-r, C-c C-e etc.) does not work.
 I.e., such binaries can only use C-c C-c (and C-c C-a) to typeset
 the latex documents.
If you consider that these incompatibilities are not acceptable,
please express your opinion.  I would be ready to discuss about this.

If no objection, I'll commit the change in a few days.  Adding document
changes and regression tests will follow later.

Best regards,
Ikumi Keita

P.S.  I tested the patch with MikTeX briefly, and encountered no
errors.

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel