Ken Moffat wrote:
OK, my initial findings from using ncursesw in the console with a
locale of en_GB.UTF-8 are that I can see zero benefit. In
particular, common West-European accented characters (e.g. the
o-umlaut in my .sig) display as multiple characters. This is no
different from how they display with the book's non-wide ncurses.
On xterms on systems with the non-wide ncurses, many of these
characters do display correctly, and I can even generate some of
them from the keyboard.
Actually, there is one benefit, nicer boxes in the kernel's
make menuconfig (they have highlights and shadows).
So, at this stage I'm not going to suggest switching to ncursesw.
Ken
From the testing I've done, I agree, but if things were more programs
were compliant with utf-8 then it would benefit us as a project, but
right now I don't see any benefit. I want to try again once the new
groff and man come out and see if we can work on that at that point.
Even then I was thinking about making the utf-8 stuff as optional.
containing the differences in notes on the pages.
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
