[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:37:57 +0000 |
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.
>
> Why demand utf-8, any encoding should be ok?
I'd thought utf-8 would be trivially convertable to the internal perl encoding.
> > * Convert the messages at the time they are output.
> >
> > For example, if a node name is in EUC-JP, this would be converted
> > (internally)
> > into UTF-8 when the file is read.
>
> Why not converted to the internal perl encoding?
This is what I had meant. The result of gettext should be Perl character
strings, not sequences of bytes. I think your idea of a filter on the output
is a good one.
- Re: Non-ASCII characters in @include search path, (continued)
- 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, 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
- 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 <=
- 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, 2022/02/21
- 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