Re: wxt terminal - questions

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

On Monday 17 April 2006 09:11 am, Timoth=E9e Lecomte wrote:

> I have implemented the behaviour described above : using the locale to
> determine the charset.=20


> I just added one other detail : when using the=20
> Symbol font, the terminal will assume you're using iso_8859_1, because
> you'll have to use non-utf8 characters.

What is "the" Symbol font, in this case? =20

The Adobe "Symbol" font, which is what most of the other drivers find by
default, is not an iso8859-1 encoding.  It is "Adobe-specific", which
causes headaches with libgd and libfreetype. =20

The Microsoft "symbol.ttf" font, on the other hand, claims to be encoding
"microsoft-symbol".

The symbol font entries in the screenshot I sent yesterday were
actual UTF-8 encoded characters.

I am uncertain how all of this will play out in practice when I'm
typing from the terminal, or running a gnuplot script.  But I guess
we'll find out.


> For example, in the demo, the=20
> integral character in \362, which is not a valid utf8 character. If the
> terminal tries to read the string in utf8, it would fail here and would
> not draw this character.

Ah. I see. So you're thinking about character data entered as octal
constants, as in charset.dem.   OK, I suppose if the user intends some
particular encoding for octal data, he should give an explicit=20
"set encoding <foo>".  Failing that, iso8859-1   (or 8859-15) is as
good a default as any.



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