4 ms·
You hit the nail on the head here. In particular the points about changing the English text and about different contexts resulting in different translations. I
by level3 11y ago
You hit the nail on the head here. In particular the points about changing the English text and about different contexts resulting in different translations.
I also feel that the gettext approach assumes everyone speaks the same base language (namely English), but that's not necessarily true with an international team. Obviously the string IDs still need to be in a common language, but those are simpler to parse and search for than full sentences, especially if the person writing the English text has chosen uncommon words or syntax.
- ngrilly 11y agoThanks! I agree with you that the gettext approach relies on the assumption that everyone speaks the same language. I would add that it also relies on the assumption that every programmer has good writing skills, which is not always the case. In my teams, some programmers are really good at writing code, but not so good at writing a correct English or French sentence. In such a situation, string IDs are better.