Re: [Tuxpaint-devel] Windows beta build to test Input Method support?

[<tor...@at...>]

I use Win2K Norwegian version, and tested the new 0.9.17 2007-04-28
Windows-version from John.
I have Norwegian, Russian and English keyboard setup in Windows, using 
alt-shift
to change between them.
It still works in TuxPaint 0.9.17.

A note about fonts though.
With Norwegian language chosen, I get these fonts:
(N=Norwegian letters, R=Russian letters, .=works, n=doesn't work)

N R Fontname
. . FreeMono (Medium)
. . FreeSans (Medium)
. . FreeSerif (Medium)
. . DejaVu Sans (Condensed)
. n Garuda (Bold)
. n ae_Nice (Regular)
n n TSCu_Comic (Normal)
. . Thryomanes (Regular)
. n TuxPaint Georgian (Regular)
. n Verajja (Regular)
. . Sazanami Gothic (Gothic-Regular)

As you can see, TSCu_Comic doesn't have the Norwegian letters, and Garuda,
ae_Nice,
TSCu_Comic, TuxPaint Georgian and  Verajja doesn't have the Russian alphabet
(Cyrillic).

When I choose Russian as language in TuxPaint, I get three fonts extra:
N R Fontname
n n SubsetForTuxPaint (Regular)
n n Nachlieli (Light)
n n Tsampa Keyboard (Regular) (not english either)

None of them support either Norwegian or Russian, and the last one 
doesn't even
have the
english letters.

So if I use Russian as language, I get 14 fonts where 8 fonts just give 
me boxes
or blanks
when typing Russian letters. They show that way in the buttons as well, 
so it's
easy to
see which fonts will work, but still not very userfriendly.

Would it be easy to set up a list of which fonts to load (for instance in the
locale directories),
maybe even with some way to add certain system fonts? Choosing system fonts in
the config-program
makes the font selection more difficult since it adds so many fonts that you
must scroll, and many
of the fonts look almost the same anyway.


Kind regards,
Tore



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.