On Sun, Mar 18, 2018 at 01:26:12PM +, Christos Zoulas wrote:
> I would just leave it broken until the perseant branch is merged :-)
> You can always fix it, buy changing the locale in the environment to one
> that works, instead of gutting it for all locales.
IIUC we have to weigh:
- the num
In article <20180318.153625.846954900.nakay...@netbsd.org>,
Takeshi Nakayama wrote:
chris...@astron.com (Christos Zoulas) wrote
>
>> In article <20180317235857.ga5...@homeworld.netbsd.org>,
>> wrote:
>> >Hi,
>> >
>> >I'm not sure what the changes affect. Does this mean UTF-8 won't work
>>
>>> chris...@astron.com (Christos Zoulas) wrote
> In article <20180317235857.ga5...@homeworld.netbsd.org>,
> wrote:
> >Hi,
> >
> >I'm not sure what the changes affect. Does this mean UTF-8 won't work
> >either? that's sounds like a big price to pay.
> >Also, the problem doesn't sound specific to
>>> m...@netbsd.org wrote
> Hi,
>
> I'm not sure what the changes affect. Does this mean UTF-8 won't work
> either? that's sounds like a big price to pay.
> Also, the problem doesn't sound specific to mdocml.
No, this is specific to mdocml. mdocml assums wchar_t's internal
representation UCS-4
In article <20180317235857.ga5...@homeworld.netbsd.org>,
wrote:
>Hi,
>
>I'm not sure what the changes affect. Does this mean UTF-8 won't work
>either? that's sounds like a big price to pay.
>Also, the problem doesn't sound specific to mdocml.
Well, yes it is a bit drastic. Perhaps it can be hand
Hi,
I'm not sure what the changes affect. Does this mean UTF-8 won't work
either? that's sounds like a big price to pay.
Also, the problem doesn't sound specific to mdocml.
Is the problem: netbsd mishandles some locales it claims to support?
On Sat, Mar 17, 2018 at 11:06:48AM +, Takeshi Naka
