Re: [Tuxpaint-devel] Re: [SDL] Bug: Problems with WinXP tablet PC cursor in fullscreen

[John P. <jo...@jo...>]

On Wed, Jan 04, 2006 at 11:20:01AM -0800, Bill Kendrick wrote:
> On Tue, Jan 03, 2006 at 12:07:48AM -0300, Gabriel Gazzán wrote:
> > I'm having problems with spanish accented characters in Tux Paint Text tool in 
> > 0.9.15-2 under Windows.
> > Accenter characters simply don't appear.
> 
> Hi Gabriel.  This is the direct fault of Tux Paint, but I'm not 100% sure
> how well the underlying SDL library can support this.  I sadly haven't
> looked into it.
> 
> I wonder, I can set up a "dead keys" system on my KDE desktop at home,
> so that if I type ['] then [a], it will show "á", for example.  However,
> I'm not sure if SDL would pick that up.
> 
> I suppose I should test it. :)
> 
Hi Bill,

I did that on Windows and tried some of the SDL test programs - they
don't work properly either.

Looking at the SDL documentation Wiki, I can't find a definitive
statement about the 'Uint16 unicode;' field in SDL_keysym. Is it correct
to assume that it is UTF8?

I'm looking at a bodge that would cause 'SDL.dll' to depend on
'libiconv-2.dll' and use it to convert from UTF-16 (NT/2K/XP) or some
horrible 8-bit (code-page) character (Win9x/ME) into UTF-8.

I would probably dump the SDL 'directx' driver at the same time as it
seems to be part of the problem.


I didn't realise that the X11 SDL backend has the same problem. I just
tried on KDE and whilst the terminal (and most of everything else) works
ok, Tux Paint and the SDL 'checkkeys' program don't.

Oh, well...

> 
> The whole issue of "I can't enter characters in [my favorite language]"
> is a known one, and has lived in the TODO list in the past, and is now
> listed in the Bug Tracker at SourceForge:
> 
>   http://sourceforge.net/tracker/index.php?func=detail&aid=1070414&group_id=66938&atid=516295
> 
> 
> -bill!

SDL_inputmethod looks like a good solution for CJK languages, but surely
SDL would benfit from working composition for e.g. Spanish?

I'll cast my eye over it (it's probably horrible, isn't it :-),

cheers,
John.