> 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?
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.
More users = more money?
>Kakaotalk is in English, French, German, Indonesian, Italian, Japanese, Korean, Portuguese, Russian, Simplified Chinese, Spanish, Thai, Traditional Chinese, Turkish, Vietnamese (https://apps.apple.com/us/app/kakaotalk/id362057947)
I used it earlier this year in Korea, although it did have a hard to get to setting to change your language, many many things were still in Korean.
It is very difficult to navigate, but I asked for help and a native was able to figure it out.
Still more usable than Google Maps though, which will only give you a not so good train schedule. No walking directions at all.
Localization is hard, even for companies that spend a lot of time and effort on it.
It isn't just string replacements!
(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...]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.