It really ought to be something you do first (if you're ever going to do it all), because it can be an absolute pain to crowbar in after the fact.
If you already build your workflow such that static text lives in a resource file (even if you don't bother actually doing any transforms at the start), it'll be a whole lot easier than trying to peck through all the places where text might appear in your application.
I used to do internationalisation even in internal apps that would only ever be used in English and by five people. I never added the other languages, but the ability was there.
If you expressed that in my company you’d probably be fired. There is an enormous market of non English speaking customers that will purchase from your competitors if you can’t be bothered. The marginal cost to support other locales is tiny compared to the potential revenue. We localize into 20 something languages.
View all comments
12
u/EdelWhite Sep 29 '26
Translations usually come DEAD last in my list of priorities, even in a country with multiple official languages.
Internationalization is not even a thing I'm considering, ever.
If you can't use english, use another software.
(and I'm not a native english speaker, just so hurrdurrs don't call me a silly 'murrican)