Bruno Haible <[EMAIL PROTECTED]>:
> Is there any reason to do things differently than in the X/Open spec?
>
> That spec is based on the cchar_t type, which contains the information
> about one screen cell (or two adjacent cells, in case of a
> double-width character). It must contain the base character,
> additional combining characters - how else could you display Thai? -
> and of course a foreground and a background color.
>
> It's not worth discussing the number of bits needed to represent a
> screen cell. The entire screen will normally be less than 132x50
> cells. It won't a big difference to programs whether that uses 3 KB or
> 15 KB.
With 24 bytes per cell it might be about 160 kB. That doesn't matter
in most cases, but maybe in some applications it's a shame to use so
much memory.
I don't like cchar_t because of the way it contains a little
fixed-length array of wchar_t. I'd prefer a more dynamic API.
Edmund
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
