-
Notifications
You must be signed in to change notification settings - Fork 69
Things to watch out for when translating Anathema
Urs Reupke edited this page Sep 8, 2012
·
1 revision
Some issues that came up while @fmneto was adding the Portuguese translation, documented for posterity:
- To get started, please read the Contributors' Quickstart
- Don't "translate" the version markers.
Some of the properties reference the currently running version. Those are critical for the internal workings, and must never be translated. - If something doesn't need translation, don't translate it.
No need to create a file, no need to create a line. Anathema falls back to the English default text. - The encoding is set.
Java properties are set to use ISO-8859-1. If you need to add UTF-8 characters, escape them as\uXXXX
, where XXXX is the UTF code. native2ascii can help you with this part. - Add your language as a choice.
Apart from adding the.properties
, you'll need to add your language to the list of supported locales
Basics
Contributors' Quickstart
Developing Anathema with Eclipse
Some notes on translations
How to release a new version
Technical Stuff
How to compile NSIS for POSIX systems
Internal Workings of the Repository
How to update the JRE
How to start a new update train
Specifics
How to add new Character Sheets