3 ms·
There's a bunch of reasons: Someone already said it, but using the same English text in two different places often needs different other language text, and tha
by toast0 4y ago
There's a bunch of reasons:
Someone already said it, but using the same English text in two different places often needs different other language text, and that's difficult if the English is your key.
When the English text changes, but the meaning doesn't, you may end up with English instead of the old translation (depends on your system).
If all your text should be ids, you can switch to a ZZ (or something) locale and should see all translation ids (or user data), and if you don't, you know you missed tagging something.
If you do want to fallback to English (or any other language) at runtime (or build time), that's something you can do without needing to have your translation keys be English text. Ideally, I'd want to have a three level check --- do I have the language and locale, if not do I have a default for the language, if not let's go with a default language (unless lang=ZZ as described earlier); but reality sometimes means you need a list of languages that aren't present but should be substituted with something close-ish. And sometimes you end up building a language picker because users may not want to use the system language in your application. i18n is a lot of fun.