In article ,
RVP wrote:
>On Wed, 30 Aug 2023, Christos Zoulas wrote:
>
>> Why don't we make next and end unsigned char so that all instances are fixed?
>>
>
>:) My original attempt did just that, but then I had to cast to char in a lot
>more places to get libc to build.
I will leave it as is for
On Wed, 30 Aug 2023, Christos Zoulas wrote:
Why don't we make next and end unsigned char so that all instances are fixed?
:) My original attempt did just that, but then I had to cast to char in a lot
more places to get libc to build.
-RVP
In article , wrote:
>On Wed, Aug 30, 2023 at 02:32:25PM -, Christos Zoulas wrote:
>> In article ,
>> RVP wrote:
>> >On Wed, 26 Jul 2023, tlaro...@polynum.com wrote:
>> >
>> >> $ export LC_CTYPE=fr_FR.ISO8859-15
>> >>
>> >> and then:
>> >>
>> >> $ echo "??" | sed 's/??\é/g'
>> >> sed: 1: "s/
> This whole "i18n" and "l10n" is a nightmare---and this is a not
> english native speaker who writes it...
And as a native anglophone - who knows a smattering of assorted other
languages - I agree.
I just recently ran into an occasion where something actually got me to
send mail to a domain whos
On Wed, Aug 30, 2023 at 02:32:25PM -, Christos Zoulas wrote:
> In article ,
> RVP wrote:
> >On Wed, 26 Jul 2023, tlaro...@polynum.com wrote:
> >
> >> $ export LC_CTYPE=fr_FR.ISO8859-15
> >>
> >> and then:
> >>
> >> $ echo "??" | sed 's/??\é/g'
> >> sed: 1: "s/??\é/g": RE error: trailing backs
In article ,
RVP wrote:
>On Wed, 26 Jul 2023, tlaro...@polynum.com wrote:
>
>> $ export LC_CTYPE=fr_FR.ISO8859-15
>>
>> and then:
>>
>> $ echo "??" | sed 's/??\é/g'
>> sed: 1: "s/??\é/g": RE error: trailing backslash (\)
>>
>
>Not running NetBSD right now, but, FreeBSD 13.2 has the same issue whi
On Wed, 26 Jul 2023, tlaro...@polynum.com wrote:
$ export LC_CTYPE=fr_FR.ISO8859-15
and then:
$ echo "??" | sed 's/??\é/g'
sed: 1: "s/??\é/g": RE error: trailing backslash (\)
Not running NetBSD right now, but, FreeBSD 13.2 has the same issue which
can be seen even with a plain grep(1)--as
