2012/5/5 Jim Graham <[email protected]> > On Sat, May 05, 2012 at 12:54:44PM -0400, Mark Murphy wrote: > > On Sat, May 5, 2012 at 12:48 PM, Jim Graham <[email protected]> > wrote: > > > If it would work, it'd certainly be a nice alternative to doing > > > all of those translations.... > > > > Um, string resources are not somehow automagically translated. The > > resource system has the notion of different resource sets based on > > language, but it is still up to you to provide translations for each > > language that you wish to support. > > 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.
As Mark already pointed out, they don't. > The implication was that they were automatically > translated, and I've worked based on the assumption that that was the > case all along. > No, it's just easier to give the translator (human or machine based) some XML files with nicely structured strings than to give them Java code. Another reason is that Android handles loading the right version of the string for you, via getString etc., so that the code doesn't have to be changed. Yet another is that someone editing your Java source for the sake of translation, if it was done that way, could accidentally mess up your code logic. .... there are probably more, I'm sure there are hundreds of thick, expensive, large-format books with pretty covers written on the topic of software localization. > > Sigh. And given the negative views towards even the translation methods > in the SDK, I guess Kostya's suggestion of "just leaving English alone" > wins. Given that I'm hoping that this app, a camera app with an emphasis > on real photography, not so much on the goofy effects, might be in the > right category (already indicated by Romain Guy as one notably missing > from the Market) to (again, HOPEFULLY) help get me out from under having > to rely on Social Security Disability (cancer #1, blah blah), or at least > pay off several thousand dollars worth of medical bills, I certainly > don't have the resources to get it all translated correctly, then. > You might want to look in Android framework and application sources for some common words / phrases. The Android license allows you to take those strings and copy into your own app. So that would be a good start. And if you ever decide to have a Russian translation, just send me your XMLs and I'll do them for you. Also of note: for some locales a two-letter language code is not enough. Consider "pt" vs "pt-rBR", also "zh-rCN", "zh-HK", "zh-rTW" just to list what comes to mind. -- K > > Thanks, > --jim > > -- > THE SCORE: ME: 2 CANCER: 0 > 73 DE N5IAL (/4) MiSTie #49997 < Running FreeBSD 7.0 > > [email protected] ICBM/Hurr.: 30.44406N 86.59909W > > Seen in alt.sysadmin.recovery: "Priceless; that's better than telling > him to use the Read Manual command with the Real Fast option." > > Android Apps Listing at http://www.jstrack.org/barcodes.html > > -- > 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 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
