[BLUEJ-126] Change character encodings for translations
The character encodings used for the translations are currently decided by the translator (usually his default character encoding). This means that the user has to use the exact same character encoding which is often not the case if the translator and user are using different operating systems.
The translations should all be forced to be ASCII with unicode escape sequence.
For the template files, they should be read as UTF8 or ASCII with unicode escapes but written with the users default encoding.
Issue metadata
- Issue type: Bug
- Priority: Medium
- Fix versions: 2.5.1