On Thu, Dec 2, 2010 at 2:37 PM, Michael Menegakis <arx...@gmail.com> wrote: > On Thu, Dec 2, 2010 at 12:38 PM, Ben Noordhuis <i...@bnoordhuis.nl> wrote: >> On Thu, Dec 2, 2010 at 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. >> >> You should probably switch to SDL_ttf[2]. > > An intermediate solution to my problem would be to support part of the > routine but properly. i.e. Have the client translate to unicode with > SDL_ttf but not yet input since that would require engine > server/client plus qvm/game code support.
Scrap that. I think FTGL is far superior. _______________________________________________ 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.
