Re: wide-char support with different builds

2025年1月21日(火) 21:38 Steve White <[email protected]>:
[...]
> The obvious, quick remedy would be to set the default configuration to be.
>         CHARACTER_SET:utf-8

I would like to second this proposal.
[I haven't had to build nkf or hobble along with iconv for well over
10 years now.  For languages that have multiple encodings, e.g.,
Japanese (euc-jp, sjis,  iso-2022-jp), utf-8 has been a blessing.]
[...]
> This ISO-8859-1 default was never a good idea, and is now a thing of the past.

I started out on an 8bit machine, but soon purchased a 16bit machine.
Even when I moved up to 32 bit, utf-8 was still pretty much out of
reach.  In those days, ISO-8859-1 was a fairly decent default, I
suppose.  I'm pretty sure, though, that most people who crank these
machines up know what they are getting into.  Truly, iso-8850-1 as the
default is a relic of the past.  My $0.02

Take care all,

Henry