CH_DISPLAY and gettext

Jeremy Allison jra at
Tue Jun 21 10:04:19 MDT 2011

On Tue, Jun 21, 2011 at 04:03:01PM +1000, tridge at wrote:
> Regarding the separation of CH_DISPLAY and CH_UNIX, Jeremy may be able
> to give more background, but I believe the separation came about
> because there were some sites in Japan which used different character
> sets for their terminals and their filesystems. This was done because
> of some legacy compatibility issues which I think originally came from
> the CAP appleshare for unix file server, which had problems with 8 bit
> unix character sets. So some weird filesystem encodings were used to
> avoid this problem, but sysadmins used terminals that had different
> encodings that were better for display.

Yes, that sounds about right as I remember it :-).

> I suspect this sort of setup is either gone completely now, or so rare
> as to hardly matter. Basically UTF-8 has won, and if you're not using
> UTF-8 on unix these days then you're pretty crazy.

Japan :-).

> So I'd support dropping CH_DISPLAY, unless someone can point out a
> good reason to keep it.

+1 on dropping CH_DISPLAY.

> It's even arguable that we could drop CH_UNIX
> and just do UTF-8 at some stage, although I suspect there are still
> sites around who use something other than UTF-8, just not sites that
> use something different for terminals and filesystems.

Japan :-). Last time I heard there were still sites using SJIS
or EUC-JP. Maybe monyo can comment ? There are also some Eastern
European sites using older char sets as we still get bugs on these.


More information about the samba-technical mailing list