I know this is a pretty old thread, but I'm curious if it is still the contention of the team at Google that changing the language at runtime is a bad idea? If so, what are my alternatives? I am doing a kisosk application for a corporate customer so I can't fire the intent to bring up the OS config menu. I did a similar product on an embedded Windows (shudder) system a few years ago and we basically just implemented our own getString(prompt_id, sel_lang) call along with a structure of flat files to represent the different languages supported. I suppose the same approach is doable on Android but I'm curious if there is something already there that I could/should be doing. Thanks!--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
No comments:
Post a Comment