I don't know much about Quake 3 (to me is still the 'new game', as I am quake1 engine coder)... but sounds like you need UTF8 support in strings. Thay may be a important (big?) architecture change, but also something that sould be tested against other clients: you don't want a guy typing a word in russian causing no-ioQuake3 engines to crash (I don't think something like that will happend, but you never know....).
How Quake3 work anyway? do it use TTF fonts? then maybe the seed for this feature is already there. As maybe a unicode complete TTF font can be used. note to self: I must learn about this new "Quake 3" game :-/ On 2 December 2010 10:56, Michael Menegakis <arx...@gmail.com> wrote: > Is it doable? I made a routine to work with Google Translate on game > chat (or explicitly with /translate <text>) but the main issue is that > mainly ASCII output is supported and input is also problematic. It > basically limits the languages it support. > > It's also important for other common uses; people simply want to type > their languages. > > One could think of Transliteration as a solution but transliteration > to ASCII is considered linguistically a murder since not only there's > no agreement on methods of transliteration but it also wrecks > languages, making it only at best a temporary solution. -- -- ℱin del ℳensaje. _______________________________________________ ioquake3 mailing list ioquake3@lists.ioquake.org http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org By sending this message I agree to love ioquake3 and libsdl.
