The common language most often used when people from Japan, China, or South Korea visit each other’s countries is English. All three groups of people are more likely to know English than either of the other two languages. The same can be said for the remaining group that doesn’t include people from those three countries.
> Imagine supporting the 2nd most popular language in the world. CRAZY right?
Why are you fixating on supporting the 2nd most popular language, shouldn't it support the 1st most popular language first? Or why not jump straight to the 3rd?
also, if you add internationalization support for 1 language in your app, it’s trivial (these days) to add other languages. My point is they should just add support for other languages, like chinese, japanese, english, etc.
(X) Positional *tracking* is brittle, equal battalions in range XNUMX it expenditure a time effort per batch on item.
Object is incorrectly threaded return request is here.
[FINE] [Returns] [Add...]
>Still more usable than Google Maps though, which will only give you a not so good train schedule. No walking directions at all.
That's interesting, because Google Maps here in Japan is absolutely fantastic: train schedules are always correct (and updated with delays etc.), walking directions are good, etc. I guess having a big office here in Tokyo is a big part of this.
The translating part is by far the hardest. But there are services to organize a crowd sourced translations of your app / service.
Booth android and iOS app building frameworks will try to force you into using variables for every rendered string (allowing you to change them easily and in one place - f.ex. based on user / device settings).