[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Non-ASCII characters in @include search path
From: |
Patrice Dumas |
Subject: |
Re: Non-ASCII characters in @include search path |
Date: |
Sat, 19 Feb 2022 23:00:33 +0100 |
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", 0x558ef4df54a8, 0) = -1
ENOENT (No such file or directory)
I think that there is some wrong encoding/decoding somewhere,
but I don't know where. It is particularly strange that I cannot
reproduce with 6.8 but Gaël can.
The strace from the devel version shows
newfstatat(AT_FDCWD, "./\303\250/toto.texi", {st_mode=S_IFREG|0644, st_size=4,
...}, 0) = 0
--
Pat
- Non-ASCII characters in @include search path, Gaël Bonithon, 2022/02/17
- Re: Non-ASCII characters in @include search path, Patrice Dumas, 2022/02/19
- Re: Non-ASCII characters in @include search path, Gaël Bonithon, 2022/02/19
- Re: Non-ASCII characters in @include search path, Gavin Smith, 2022/02/19
- Re: Non-ASCII characters in @include search path, Patrice Dumas, 2022/02/19
- Re: Non-ASCII characters in @include search path,
Patrice Dumas <=
- Re: Non-ASCII characters in @include search path, Gavin Smith, 2022/02/20
- Re: Non-ASCII characters in @include search path, Gavin Smith, 2022/02/20
- Re: Non-ASCII characters in @include search path, Gavin Smith, 2022/02/20
- Re: Non-ASCII characters in @include search path, Patrice Dumas, 2022/02/20
- Re: Non-ASCII characters in @include search path, Patrice Dumas, 2022/02/20
- Re: Non-ASCII characters in @include search path, Gavin Smith, 2022/02/20
- Re: Non-ASCII characters in @include search path, Patrice Dumas, 2022/02/20
- Re: Non-ASCII characters in @include search path, Eli Zaretskii, 2022/02/20
- Re: Non-ASCII characters in @include search path, Patrice Dumas, 2022/02/20
- Re: Non-ASCII characters in @include search path, Gavin Smith, 2022/02/20