Re: wxt terminal - questions

[Ethan A M. <merritt@u.washington.edu>]

On Sunday 16 April 2006 08:35 pm, Timoth=C3=A9e Lecomte wrote:

> I can implement the following :
> - if the user has used "set encoding ..." where "..." is something
> different from "default", the terminal converts from this encoding to utf8
> - otherwise, use the 'locale' to determine the input charset, and assume
> this is the input encoding for the conversion to utf8.

Or at the least, if 'locale' reports any flavor of utf8 then do not do
any conversion.

> However, I am still not clear on one thing :
> If you launch the demo 'charset.dem' :
> - with the current code, the wxt terminal will show all characters as
> iso8859-1 encoded.

Correct.

> - with the new code falling back to the 'locale' charset, and if your
> locale charset is UTF-8, you won't see the last four lines [upper bit set]
>=20
> At the same time, the X11 terminal will show these lines !!! So my
> question is : what is the X11 terminal doing ??

The X terminal chooses an iso-8859-1 font by default unless you tell
it explicitly to use a multibyte font.  If you say
	set term x11 font "mbfont:verdana"
then as you predict, the last four lines of charset.dem are blank.
However, in this mode it handles utf-8 characters properly.

I should add a "utf8.dem" as well.
Here's a quick version, and a screen shot from=20

    set term x11 font "mbfont:sazanami mincho,vera,20"
    load 'utf8.dem'

> Chris has already answered, and I can only confirm. Cairo has definetely
> been designed with alpha transparency in mind.

Great.  But that's not a project for 4.2.

=2D-=20
Ethan A Merritt
Biomolecular Structure Center
University of Washington, Seattle 98195-7742