On Sat, May 5, 2012 at 1:10 PM, Jim Graham <[email protected]> wrote: > Strange. I read just the opposite: that you should put strings in > strings.xml so they'll get translated for you, instead of putting them > in the Java code. The implication was that they were automatically > translated, and I've worked based on the assumption that that was the > case all along.
The only way that would work is via machine translation, discussed elsewhere in this thread. MOTODEV Studio for Android will help you translate string resources via Google Translate, but that's about it in terms of automatic tool support. For simple prompts, I seem to recall running across some sites offering translation assistance, but I doubt they are designed for full-on help text and such. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 3.7 Available! -- 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
