TGE uncompatible with SDL 1.2.10
by Alexander Maltsev · in Torque Game Engine · 07/27/2006 (1:21 pm) · 4 replies
TGE uses some functions from SDL's internal API, and this API was changed in SDL 1.2.10. Now SDL doesn't have X11_KeyToUnicode function, and TGE doesn't works. When new SDL will be supported?
SDL 1.2.10 has many improvements in unicode support, so it very important, imho
SDL 1.2.10 has many improvements in unicode support, so it very important, imho
#2
I know that almost impossible to use unicode input with SDL <= 1.2.9. Sad.. :\
08/04/2006 (9:59 pm)
Thanks. But what about unicode? Seems like unicode input unsupported (english input at all keyboard layouts)...I know that almost impossible to use unicode input with SDL <= 1.2.9. Sad.. :\
#3
enter dead keys in torque (like french accents). I had to rewrite some
code in the xf86 specific part of the engine to manage dead keys
myself.
Torque can display unicode strings in its last incarnation but
(somebody more skilled than me may say otherwise),
unicode input does not work on linux as far as I know
given the use made of SDL (keycode are used, killing
the unicode information).
my understanding is that with some pain and code
writing you can manage input with western langages,
but multi-byte languages like chinese, japanese or korean
are hopeless with the torque current implementation.
Pascal
08/06/2006 (7:52 am)
I had the same problem than you one year ago : no way for example toenter dead keys in torque (like french accents). I had to rewrite some
code in the xf86 specific part of the engine to manage dead keys
myself.
Torque can display unicode strings in its last incarnation but
(somebody more skilled than me may say otherwise),
unicode input does not work on linux as far as I know
given the use made of SDL (keycode are used, killing
the unicode information).
my understanding is that with some pain and code
writing you can manage input with western langages,
but multi-byte languages like chinese, japanese or korean
are hopeless with the torque current implementation.
Pascal
#4
If someone does have expertise in this area we'd LOVE to work with them to get this area of the engine more solid!
Just to note - all the interfaces are in for this to happen, and the core engine code supports it. It's just a matter of writing the glue code to get Torque and Linux to talk.
08/10/2006 (3:24 pm)
The windows side works fine - so all that the Linux port needs is someone to step up to the plate, research the IME solutions, and implement one. When we did the Unicode work we couldn't find a good reference on how to do it on Linux in a way that wouldn't break for every different distro out there... so we just left it as is.If someone does have expertise in this area we'd LOVE to work with them to get this area of the engine more solid!
Just to note - all the interfaces are in for this to happen, and the core engine code supports it. It's just a matter of writing the glue code to get Torque and Linux to talk.
Torque Owner Pascal Ognibene
for now, if you want Torque to run properly you can do:
export LD_LIBRARY_PATH=$TORQUE_HOME/lib/sdl/linux:$LD_LIBRARY_PATH
before running the torque executable. This will use the sdl version
shipped with Torque (presumably < 1.2.10).
Now if you want to recompile the engine you must make sure that you use
a similar version at link time.
Pascal