Overview
Artifact ID: | 7983383402d5557845a6ecaffd449fa3fcf52682 |
---|---|
Ticket: | 91683f49e8c168ba8f349a1e83cc36a2b7b249c1
Mechanism for i18n the product UI |
User & Date: | anonymous 2010-02-19 12:29:49 |
Changes
- Appended to comment:
<hr><i>anonymous added on 2010-02-19 12:29:49:</i><br> Whilst gettext is certainly a good practice towards i18n/l13n, it's certainly not the be-all and end-all of dealing with multiple languages. I'd be in favour of the languages being done at compile time, not inside the repository as much as possible. Constants, templates and lots of #define are suitable work arounds.