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

2022-02-19 Thread Eli Zaretskii
> Date: Sat, 19 Feb 2022 23:28:43 +0100 > From: Patrice Dumas > > Info: always ignore text before the first @node or sectioning command. There are directives there that cannot be ignored, so I'm not sure I understand what you mean by "ignore". Please elaborate. Maybe you should show a complete

Re: Non-ASCII characters in @include search path

2022-02-19 Thread Gaël Bonithon
It doesn't seem to depend on the version of Texinfo for me. I had tried downgrading to versions 6.6 and 6.7 during the Octave problem cited in my first post, and I tried earlier by building from the latest commit 091f22068c for the test case in this thread, with still the same result. Here are t

Re: Non-ASCII characters in @include search path

2022-02-19 Thread Gaël Bonithon
> export TEXINFO_XS=omit > makeinfo -I ./è simplest.texi It's all the same. My file system is ext4. Cheers, Gaël --- Original Message --- On Saturday, February 19th, 2022 at 9:24 PM, Patrice Dumas wrote: > Hello, > > I have no clue about what could be going on. One thing you could >

more consistent ignoring before node and sections and Top node

2022-02-19 Thread Patrice Dumas
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 informations in @titlepage that are not truly title page (@insertcopying + publishing info), and also for the Top node. It is this way to cope bot

Re: Non-ASCII characters in @include search path

2022-02-19 Thread Patrice Dumas
On Sat, Feb 19, 2022 at 10:30:00PM +0100, Patrice Dumas wrote: > > I could reproduce with texinfo 6.7 rebuilt from source, though. This is very strange. I can reproduce with the perl parser too. Everything seems ok. I did a strace, there is newfstatat(AT_FDCWD, "\303\203\302\250/toto.texi", 0x

Re: Non-ASCII characters in @include search path

2022-02-19 Thread Patrice Dumas
On Sat, Feb 19, 2022 at 09:24:00PM +, Gavin Smith wrote: > On Sat, Feb 19, 2022 at 06:04:32PM +, Gaël Bonithon wrote: > > Does not work for me (I'm on Arch Linux, Texinfo 6.8): > > > > $ makeinfo -I ./è simplest.texi > > simplest.texi:10: @include: could not find toto.texi > > $ makeinfo -

Re: Non-ASCII characters in @include search path

2022-02-19 Thread Gavin Smith
On Sat, Feb 19, 2022 at 06:04:32PM +, Gaël Bonithon wrote: > Does not work for me (I'm on Arch Linux, Texinfo 6.8): Just saw this bit. I will have to test with Texinfo 6.8 and see if the issue replicates itself. If not, then there is likely some unresolved issue.

Re: Non-ASCII characters in @include search path

2022-02-19 Thread Patrice Dumas
Hello, I have no clue about what could be going on. One thing you could attempt, to determine if there is the same issue with the pure perl implementation, would be to do export TEXINFO_XS=omit makeinfo -I ./è simplest.texi And report if there is the same issue. Not sure if this is gonne be re

Re: Non-ASCII characters in @include search path

2022-02-19 Thread Gavin Smith
On Sat, Feb 19, 2022 at 06:04:32PM +, Gaël Bonithon wrote: > Does not work for me (I'm on Arch Linux, Texinfo 6.8): > > $ makeinfo -I ./è simplest.texi > simplest.texi:10: @include: could not find toto.texi > $ makeinfo --html -I ./è simplest.texi > simplest.texi:10: @include: could not find t

Re: Non-ASCII characters in @include search path

2022-02-19 Thread Gaël Bonithon
Does not work for me (I'm on Arch Linux, Texinfo 6.8): $ makeinfo -I ./è simplest.texi simplest.texi:10: @include: could not find toto.texi $ makeinfo --html -I ./è simplest.texi simplest.texi:10: @include: could not find toto.texi $ However: $ cp -r è e $ makeinfo -I ./e simplest.texi $ makeinfo

Re: Feature request: api docs

2022-02-19 Thread Patrice Dumas
On Mon, Feb 07, 2022 at 08:37:15AM +, Reißner Ernst wrote: > I must correct myself: @result and @error are not usable, > Because it has also semantics and within apidocs this would be misuse. > I think @param, @return and @throws would be fine at least for functions. > The above shall be to

Re: Feature request: api docs

2022-02-19 Thread Patrice Dumas
On Mon, Feb 07, 2022 at 08:30:15AM +, Reißner Ernst wrote: > > Well, I think texinfo was used for general api docs but mostly lisp. > I think you are right, there are many features which allow also formatting > Of api docs, but as you say, without semantics. > I think it is a bad idea, to p

Re: Non-ASCII characters in @include search path

2022-02-19 Thread Patrice Dumas
On Thu, Feb 17, 2022 at 07:53:16AM +, Gaël Bonithon wrote: > Hello, > > It seems that makeinfo does not support non-ASCII characters in directory > names added to the @include search path. > > If this is intentional, I could not find any trace of it in the documentation. > If it's not docume