Re: Non-ASCII characters in @include search path

2022-02-23 Thread Eli Zaretskii
> From: Gavin Smith > Date: Wed, 23 Feb 2022 20:38:08 + > Cc: pertu...@free.fr, trash.parad...@protonmail.com, bug-texinfo@gnu.org > > > Are you describing what we will do in makeinfo, or are you describing > > how the current makeinfo, which doesn't re-encode file names, works? > > > > If t

Re: AW: Feature request: api docs

2022-02-23 Thread Jacob Bachmeyer
Reißner Ernst wrote: [...] All of these markup is not presentational like @table, it is content markup, descriptive or even procedural. It allows other tools not only to render, but to analyze and to verify. I also strongly disagree that this kind of markup is really language specific. Parame

Re: Non-ASCII characters in @include search path

2022-02-23 Thread Gavin Smith
On Wed, Feb 23, 2022 at 09:52:21PM +0200, Eli Zaretskii wrote: > > E.g. - UTF-8 Texinfo file, processed under KOI-8 locale on Windows, > > accessing filenames named with UTF-16 filenames on Windows filesystem. > > Then the UTF-8 filenames would be encoded to KOI-8, and then some file > > access lay

Re: Non-ASCII characters in @include search path

2022-02-23 Thread Eli Zaretskii
> From: Gavin Smith > Date: Wed, 23 Feb 2022 19:31:52 + > > Whatever we do, it should be concordant with TeX's filename handling. > I imagine that TeX (except possibly on MS-Windows) would just use the > bytes, so so should we. AFAIK, TeX uses bytes everywhere. > In any case the cases we ar

Re: Non-ASCII characters in @include search path

2022-02-23 Thread Gavin Smith
On Wed, Feb 23, 2022 at 03:39:23PM +0100, Patrice Dumas wrote: > On Tue, Feb 22, 2022 at 08:52:56PM +, Gavin Smith wrote: > > > > I've done more tonight but I still have more to do. There will have to > > be some decoding of filenames when they are being put into > > an error message (e.g. "@

Re: Non-ASCII characters in @include search path

2022-02-23 Thread Gaël Bonithon
--- Original Message --- On Wednesday, February 23rd, 2022 at 2:39 PM, Patrice Dumas wrote: > > I commited a temporary 'fix' by encoding to utf8 to have the same result for > the XS and NonXS parser, it should be ok until you do a better fix with > a better interface. I can confirm that

Re: Non-ASCII characters in @include search path

2022-02-23 Thread Patrice Dumas
On Tue, Feb 22, 2022 at 08:52:56PM +, Gavin Smith wrote: > > I've done more tonight but I still have more to do. There will have to > be some decoding of filenames when they are being put into > an error message (e.g. "@include: could not find..." and possibly others). > It would make sense t