[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Non-ASCII characters in @include search path
From: |
Gavin Smith |
Subject: |
Re: Non-ASCII characters in @include search path |
Date: |
Mon, 21 Feb 2022 21:29:06 +0000 |
On Mon, Feb 21, 2022 at 08:46:56PM +0000, 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 +0000, 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
> > > UTF-8.
> >
> > I just commited input decoding (command line, environment, translated
> > messages) and output messages encoding. I left file names as is, but
> > prepared a customization variable for them.
> >
> > Now the error message is:
> >
> > testé.texi:8: warning: nœud « ésseulé » non référencé
>
> One way of fixing this would be to store the filename separately along with
> the rest of the error message, and prepend the filename when it is output.
> I can try to implement this.
Done in commit 73e922d68b. There will be a few other places where filenames
can find their way into error messages (e.g. include file not found) which
will have to be fixed separately.
- Re: Non-ASCII characters in @include search path, (continued)
- 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
- Re: Non-ASCII characters in @include search path, Gavin Smith, 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/21
- 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/21
- Re: Non-ASCII characters in @include search path,
Gavin Smith <=
- Re: Non-ASCII characters in @include search path, Patrice Dumas, 2022/02/21
- Re: Non-ASCII characters in @include search path, Patrice Dumas, 2022/02/21
- Re: Non-ASCII characters in @include search path, Gavin Smith, 2022/02/22
- Re: Non-ASCII characters in @include search path, Patrice Dumas, 2022/02/22
- Re: Non-ASCII characters in @include search path, Patrice Dumas, 2022/02/23
- Re: Non-ASCII characters in @include search path, Gaël Bonithon, 2022/02/23
- Re: Non-ASCII characters in @include search path, Gavin Smith, 2022/02/23
- Re: Non-ASCII characters in @include search path, Eli Zaretskii, 2022/02/23
- Re: Non-ASCII characters in @include search path, Gavin Smith, 2022/02/23
- Re: Non-ASCII characters in @include search path, Eli Zaretskii, 2022/02/24