Re: use ENABLE_ENCODING for Info only

2022-12-25 Thread Patrice Dumas
On Sun, Dec 25, 2022 at 10:03:51PM +, Gavin Smith wrote: > On Sun, Dec 25, 2022 at 10:45:04PM +0100, Patrice Dumas wrote: > > Hello, > > > > If I recall well, there was some previous discussions, I believe Gavin > > proposed something similar. > > > > As it is now --enable-encoding (ENABLE_EN

Re: use ENABLE_ENCODING for Info only

2022-12-25 Thread Gavin Smith
On Sun, Dec 25, 2022 at 10:45:04PM +0100, Patrice Dumas wrote: > Hello, > > If I recall well, there was some previous discussions, I believe Gavin > proposed something similar. > > As it is now --enable-encoding (ENABLE_ENCODING customization option) > means something very different for Info/Plai

Re: Weird TeX behaviour with predumped format

2022-12-25 Thread Gavin Smith
On Sun, Dec 25, 2022 at 07:26:17PM +0100, Andreas Schwab wrote: > On Dez 25 2022, Gavin Smith wrote: > > > It appears as if the line on the ** prompt is being expanded, including > > the newline at the end. > > After processing the optional &format, if the next character isn't an > escape charact

use ENABLE_ENCODING for Info only

2022-12-25 Thread Patrice Dumas
Hello, If I recall well, there was some previous discussions, I believe Gavin proposed something similar. As it is now --enable-encoding (ENABLE_ENCODING customization option) means something very different for Info/Plaintext and HTML/XML based formats. For Info/Plaintext is means using actual c

Re: Weird TeX behaviour with predumped format

2022-12-25 Thread Andreas Schwab
On Dez 25 2022, Gavin Smith wrote: > It appears as if the line on the ** prompt is being expanded, including > the newline at the end. After processing the optional &format, if the next character isn't an escape character then an implicit \input is prepended. After that the line is processed nor

Weird TeX behaviour with predumped format

2022-12-25 Thread Gavin Smith
I found some strange behaviour when testing Texinfo as a pre-dumped TeX format If the format file gives newline an active definition, the expansion can be used for the filename when loading a file with the format. Here's an attempt at a minimal example: $ cat format.tex \input plain \def\r

Re: texinfo.tex: non-ASCII support completely broken for XeTeX and LuaTeX

2022-12-25 Thread Werner LEMBERG
> All the characters work with "@documentencoding UTF-8". UTF-8 is > supposed to be the default input encoding but evidently this isn't > the case for XeTeX and LuaTeX. OK. > I have tested the change below both with and without the > @documentencoding declaration as well as with @documentencod

Re: texinfo.tex: non-ASCII support completely broken for XeTeX and LuaTeX

2022-12-25 Thread Gavin Smith
On Sun, Dec 25, 2022 at 07:19:01AM +, Werner LEMBERG wrote: > > [texinfo.tex 2022-12-19.22] > > > Consider this input file > > ``` > \input texinfo > ยท > @bye > ``` > > (the character is U+00B7, MIDDLE DOT). Only pdfTeX produces this > character; both XeTeX and LuaTeX silently discard it.