latimerius wrote: > True, if you are able/willing to supply a text renderer with your app > surely there's nothing in devices that would prevent it from rendering any > language independent of what the platform supports. And if I was working > on something that relied on text rendering as its core feature (say an > old-style adventure game or indeed Google Translate) it would make sense > for me to either write such a renderer or get a third-party one. >
My comments were not limited to text rendering and fonts. IMEs figure in there as well. > > However, what I'm afraid I just implied but failed to point out is that > I'd like to avoid any of that. I don't want to write or shop for a text > rendering module, I don't even want to bother to supply fonts with the app. > I'd just like to use what the platform already has, otherwise forget it. > This whole effort is only meant to support users who have their device in > one locale but want our app to use another one. > Again, we're not talking about mere text rendering. The point is that "Languages & inputs" is not a final authority on what is available on the device. For example, I have "fr_FR" on an Android phone here, showing all prompts in French at the system and app level (for apps with that locale programmed), yet the only languages showing in the "Langue" prompt are "English" and "Español". So your idea won't work. -- Lew On Wed, Jun 12, 2013 at 9:36 PM, Lew <[email protected] <javascript:>>wrote: > >> latimerius wrote: >> >>> Thanks for the reply. To explain a bit further: the reason I'm trying >>> to get something similar to what the user sees in "Language & input" is, I >>> just consider it unlikely that a device would offer a language that's it's >>> not capable to handle, or that it would *not* offer a language it *can* >>> handle. >>> >> >> What the device *offers* is a combination of what came with it from the >> OEM and >> what the user added, subject to any device-specific limitations. >> >> What the device *accepts* is a superset of what has already been >> installed. >> >> It is not only likely, but common that a device will have apps and device >> configurations >> supporting locales beyond what originally came with the device. >> >> I've got Google Translate on my phone. It supports many locales not on my >> L&I screen. >> >> I've also loaded programs that take over the IMEs and display for >> whatever language >> and thrown the whole phone into Arabic, Chinese, Korean or whatever. >> >> Piren laid out a taxonomy of locale support. Basically an app will >> support any >> locale it's properly configured to support. >> >> -- >> Lew >> >> -- >> -- >> You received this message because you are subscribed to the Google >> Groups "Android Developers" group. >> To post to this group, send email to >> [email protected]<javascript:> >> To unsubscribe from this group, send email to >> [email protected] <javascript:> >> For more options, visit this group at >> http://groups.google.com/group/android-developers?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "Android Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
