Re: Non-ASCII characters in @include search path

2022-02-21 Thread Eli Zaretskii
> From: Gavin Smith > Date: Mon, 21 Feb 2022 21:42:14 + > Cc: pertu...@free.fr, trash.parad...@protonmail.com, bug-texinfo@gnu.org > > On Sun, Feb 20, 2022 at 05:07:32PM +0200, Eli Zaretskii wrote: > > > Do you know if TeX distributions for Windows do any handling of filename > > > encodings?

Re: more consistent ignoring before node and sections and Top node

2022-02-21 Thread Patrice Dumas
On Sun, Feb 20, 2022 at 10:42:25AM +, Gavin Smith wrote: > On Sat, Feb 19, 2022 at 11:28:43PM +0100, Patrice Dumas wrote: > > Hello, > > > > Right now there is a diversity of handling of text at the beginning of > > Texinfo manuals, before the first @node and sectioning, but also for the > > i

Re: Non-ASCII characters in @include search path

2022-02-21 Thread Patrice Dumas
On Mon, Feb 21, 2022 at 11:34:00PM +0100, Patrice Dumas wrote: > On Mon, Feb 21, 2022 at 09:29:06PM +, Gavin Smith wrote: > > > > Done in commit 73e922d68b. > > I would prefer to have the line numbers in tests, I'll have a look at > it, but this should be doable without changing the spirit of

Re: Non-ASCII characters in @include search path

2022-02-21 Thread Patrice Dumas
On Mon, Feb 21, 2022 at 09:29:06PM +, Gavin Smith wrote: > > Done in commit 73e922d68b. I would prefer to have the line numbers in tests, I'll have a look at it, but this should be doable without changing the spirit of the commit. > There will be a few other places where filenames > can find

Re: Non-ASCII characters in @include search path

2022-02-21 Thread Patrice Dumas
On Mon, Feb 21, 2022 at 08:46:56PM +, Gavin Smith wrote: > On Sun, Feb 20, 2022 at 10:32:00PM +0100, Patrice Dumas wrote: > > On Sun, Feb 20, 2022 at 05:27:51PM +, Gavin Smith wrote: > > > If the error message became something like > > > > > > "nœud « �sseul� » non référencé" > > > > > >

Re: Non-ASCII characters in @include search path

2022-02-21 Thread Gavin Smith
On Sun, Feb 20, 2022 at 05:07:32PM +0200, Eli Zaretskii wrote: > > Do you know if TeX distributions for Windows do any handling of filename > > encodings? > > I never used non-ASCII variant of TeX (XeTeX, I guess?) on Windows, so > I don't know, sorry. It's standard TeX that processes bytes with

Re: Non-ASCII characters in @include search path

2022-02-21 Thread Gavin Smith
On Sun, Feb 20, 2022 at 07:34:49PM +0100, Patrice Dumas wrote: > > So my best idea at the moment for fixing the encoding of the error messages > > is: > > * When calling gettext and related functions, always demand UTF-8, and > > convert > > this back into Perl's internal coding afterwards. > >

Re: Non-ASCII characters in @include search path

2022-02-21 Thread Gavin Smith
On Mon, Feb 21, 2022 at 08:46:56PM +, Gavin Smith wrote: > On Sun, Feb 20, 2022 at 10:32:00PM +0100, Patrice Dumas wrote: > > On Sun, Feb 20, 2022 at 05:27:51PM +, Gavin Smith wrote: > > > If the error message became something like > > > > > > "nœud « �sseul� » non référencé" > > > > > >

Re: Non-ASCII characters in @include search path

2022-02-21 Thread Gavin Smith
On Sun, Feb 20, 2022 at 10:32:00PM +0100, Patrice Dumas wrote: > On Sun, Feb 20, 2022 at 05:27:51PM +, Gavin Smith wrote: > > If the error message became something like > > > > "nœud « �sseul� » non référencé" > > > > then encoding this to UTF-8 would break the parts which already were in > >