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.
1. UTF-8 is backwards compatible with ASCII and nul byte safe. That's a plus. 2. Input is platform dependent. I don't know of any (lightweight) libraries that cover that for you[1]. 3. Output is currently done with a simple glyph lookup (gfx/2d/bigchars.tga in pak0.pk3). You should probably switch to SDL_ttf[2]. [1] There is SDL-IM - http://sdl-im.csie.net/ - but I don't think it's maintained. [2] http://www.libsdl.org/projects/SDL_ttf/ _______________________________________________ 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.
