Re: wcwidth and glibc 2.2

[Markus Kuhn <Markus.Kuhn@xxxxxxxxxxxx>]

Bruno Haible wrote on 2001-01-12 14:39 UTC:
> > I would much favour if glibc had only two wcwidth definitions and
> > used these in *all* locales, irrespective of the encoding.
> 
> The wcwidth definition in the EUC-JP locale is given by the fact, that
> outputting a JIS X 0208 or JIS X 0212 character in kterm or similar
> terminal emulators needs two columns. You can't change that just
> because of xterm. It's xterm which has to adapt to these locales.

But why isn't it sufficient to simply use exactly the two conventions

  wcwidth()
  wcwidth_cjk()

as they are now both defined in

  http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c

I had hoped that with wcwidth_cjk(), xterm will columnwise feel very
much like kterm under EUC now. No need for many many different
locale-dependent wcwidth definitions. Having only two wcwidth() variants
is already more than enough IMHO.

The new 

  http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c

now also makes Cf characters and ZERO WIDTH SPACE zero width and Hangul
medial and final Jamos as well (as suggested by Ottfried some time ago).

And other suggestions for this hardwired wcwidth() reference
implementation?

Markus

-- 
Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK
Email: mkuhn at acm.org,  WWW: <http://www.cl.cam.ac.uk/~mgk25/>

-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/lists/