@dunmalg I guess that I find odd is that, at least for Java, i18n is really the design goal. Most web frameworks provided that ability. Wicket, Spring, etc. JSPs had tags that knew how to fish out content based on local. Android has is built in with English as the default, but with localization being additive. Heck, I'm doing that right now on my Android app.
As for Engrish, why is that bad on a first release. Yes, American's will laugh at it, but I doubt it will be enough to kill something that provide real value. Heck, Americans produce Engrish. That's never stopped us. If a German company tried to get ok English for their service/app/whatever version 1.0, they could take the money and improve for 1.4.
As for Engrish, why is that bad on a first release. Yes, American's will laugh at it, but I doubt it will be enough to kill something that provide real value. Heck, Americans produce Engrish. That's never stopped us. If a German company tried to get ok English for their service/app/whatever version 1.0, they could take the money and improve for 1.4.