In my experience, Russian and Portuguese seem to do very well, much better than German. Android seems to be popular in both of those countries, and people tend to speak no English.
There is a lot more to localization than translation.... The translation part is easy. On Feb 12, 10:39 pm, Kostya Vasilyev <[email protected]> wrote: > The Market Console has download statistics broken down per language and > per country, for your app, vs. all apps in the same category. That would > be a good starting point with deciding which language to support next. > > Other than that, I'd consider German (largest economy in Europe), and > Spanish (potential users all around the world, including the US). > > Once you've got the initial localization done, you can use the new (as > of ADT 16) Lint tool to find missing translations as you add more > baseline, US-English strings. > > The language-based resource qualifiers do work exactly as advertised, so > there aren't really any technical challenges here (or at least I haven't > run into them with my apps). > > -- Kostya > > 12.02.2012 15:29, decastro пишет: > > > I have recently released my first game app (in English) and am now > > considering whether our not I should go to the trouble of converting > > it for other languages. I would like to hear about people's practical > > experience of the process.. for example, were there any unexpected > > problems to look out for. What languages were most/least successful. > > Was it worth effort? Has someone written about three process in a blog > > somewhere? > > -- > Kostya Vasilyev -- 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
