3 ms·
This. Especially the localization bit. I'm constantly surprised to encounter folks that never even think about it, until version 1.5, and then find out that lo
by ChrisMarshallNY 6y ago
This.
Especially the localization bit. I'm constantly surprised to encounter folks that never even think about it, until version 1.5, and then find out that localization is a nightmare to add, after the fact.
And getting folks to work with them, is just as nightmarish.
Good RoT for localization is native, local speaker of the language, and dialects need to be considered. It's quite possible to bust your ass, getting a Spanish translation, only to have a lot of upset Latin-American users, because the translation was done in Castilian Spanish, as the only person who could handle the tech involved in localization was a CS student in Madrid.
I've learned to factor localization in from the beginning; even if I'm sure that this will never be used outside of my country (which isn't actually fair. There's neighborhoods in Brooklyn, where English is not the primary language; even though everyone was born here).
You just need to get to the point where you have to add localization after the fact –once, to get religion.
Localization is difficult and expensive. If we want people to help us localize, it is incumbent upon us to make it easy and relatively tech-free.
Or we can pay beaucoup bucks to iBabble-On (who do a great job, but not for free).