Difference between revisions of "Translations (OpenXcom)"
Jump to navigation
Jump to search
m |
|||
| Line 1: | Line 1: | ||
| − | Like [[GeoScape String Files|the original]], OpenXcom supports translation of all ingame strings. However, the format has been changed to make it easier to edit, maintain and add support for Unicode. | + | Like [[GeoScape String Files|the original]], OpenXcom supports translation of all ingame strings. However, the format has been changed to make it easier to edit, maintain and add support for Unicode. Currently the easiest way to translate is to use the [http://www.getlocalization.com/openxcom/ online tool]. |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Guidelines == | == Guidelines == | ||
* Don't add linebreaks: The game automatically word-wraps text, and any explicit linebreaks are marked with {NEWLINE} and {SMALLLINE}. | * Don't add linebreaks: The game automatically word-wraps text, and any explicit linebreaks are marked with {NEWLINE} and {SMALLLINE}. | ||
| − | * Preserve the original structure: | + | * Preserve the original structure: Don't change text inside {} tags and keep any spaces, uppercases, etc. that the original string has, don't go trimming and cleaning up for no good reason. |
* Be consistent: Don't make the text look schizophrenic, stick to one style throughout. If a word has multiple translations, choose one and stick with it. If working with multiple translators, be sure to work this out before-hand. | * Be consistent: Don't make the text look schizophrenic, stick to one style throughout. If a word has multiple translations, choose one and stick with it. If working with multiple translators, be sure to work this out before-hand. | ||
* Don't use an automatic translator: We're not robots. | * Don't use an automatic translator: We're not robots. | ||
* Review your work: Again, we're not robots and make mistakes every now and then. Don't forget to use a spellchecker. | * Review your work: Again, we're not robots and make mistakes every now and then. Don't forget to use a spellchecker. | ||
| − | * Pay attention to length: while most of the interface is fairly roomy (eg. Ufopaedia screens), some elements just can't fit a lot of words into a tight 320x200 screen (eg. columned lists). Remember you can test your translation ingame | + | * Pay attention to length: while most of the interface is fairly roomy (eg. Ufopaedia screens), some elements just can't fit a lot of words into a tight 320x200 screen (eg. columned lists). Remember you can test your translation ingame by downloading the file to your Language folder. |
== Graphics == | == Graphics == | ||
| − | Sadly a translator's job isn't just replacing strings. Sometimes you also need to have a little bit of artistry. | + | Sadly a translator's job isn't just replacing strings. Sometimes you also need to have a little bit of artistry. The game uses bitmap fonts to display text, so if your language has new characters that it doesn't support, you'll have to add them in yourself. The font files are PNG images in the Llanguage folder, which are referenced by a ''Font.dat'' text file which contains all the characters in the fonts (in UTF-8). To add a character you just put it at the end of the ''chars:'' in ''Font.dat'' and then draw them into the font files (both lowercase and uppercase). |
| − | + | == Format == | |
| − | + | Language files are stored in YAML format (UTF-8). Here's a typical language file: | |
| − | + | <pre> | |
| + | en-US: | ||
| + | STR_AVENGER_UFOPEDIA: "TRANSPORTER AND COMBAT SPACECRAFT. THE ULTIMATE REPLICATION OF ALIEN TECHNOLOGY." | ||
| + | STR_INTERCEPTOR_UFOPEDIA: "COMBAT AIRCRAFT WITH DUAL PULSE DETONATION ENGINES AND SPECIALLY SHIELDED ELECTRONIC SYSTEMS. THE BEST AVAILABLE EARTH BASED TECHNOLOGY." | ||
| + | STR_LIGHTNING_UFOPEDIA: "TRANSPORTER AND COMBAT CRAFT. A CRUDE BUT EFFECTIVE REPLICATION OF ALIEN PROPULSION SYSTEMS." | ||
| + | STR_SKYRANGER_UFOPEDIA: "TROOP TRANSPORTER. THE FASTEST OF ITS KIND, WITH VERTICAL TAKE OFF AND LANDING (V.T.O.L.) CAPABILITY." | ||
| + | STR_FIRESTORM_UFOPEDIA: "COMBAT CRAFT. THIS ONE-MAN FIGHTER REPLICATES THE CLASSIC ALIEN FLYING SAUCER DESIGN, WITH CENTRAL PROPULSION UNIT." | ||
| + | ... | ||
| + | </pre> | ||
| − | + | The first line contains the [http://www.i18nguy.com/unicode/language-identifiers.html IETF language tag] (same as the filename). The rest of the text are just key-string pairs, separated by linebreaks. Language files are placed in the ''Data\Language'' folder and have the .yml extension. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== External Links == | == External Links == | ||
* [http://openxcom.org/forum/index.php/board,6.0.html Translations forum] | * [http://openxcom.org/forum/index.php/board,6.0.html Translations forum] | ||
| − | |||
[[Category:OpenXcom]] | [[Category:OpenXcom]] | ||
Revision as of 17:14, 28 September 2013
Like the original, OpenXcom supports translation of all ingame strings. However, the format has been changed to make it easier to edit, maintain and add support for Unicode. Currently the easiest way to translate is to use the online tool.
Guidelines
- Don't add linebreaks: The game automatically word-wraps text, and any explicit linebreaks are marked with {NEWLINE} and {SMALLLINE}.
- Preserve the original structure: Don't change text inside {} tags and keep any spaces, uppercases, etc. that the original string has, don't go trimming and cleaning up for no good reason.
- Be consistent: Don't make the text look schizophrenic, stick to one style throughout. If a word has multiple translations, choose one and stick with it. If working with multiple translators, be sure to work this out before-hand.
- Don't use an automatic translator: We're not robots.
- Review your work: Again, we're not robots and make mistakes every now and then. Don't forget to use a spellchecker.
- Pay attention to length: while most of the interface is fairly roomy (eg. Ufopaedia screens), some elements just can't fit a lot of words into a tight 320x200 screen (eg. columned lists). Remember you can test your translation ingame by downloading the file to your Language folder.
Graphics
Sadly a translator's job isn't just replacing strings. Sometimes you also need to have a little bit of artistry. The game uses bitmap fonts to display text, so if your language has new characters that it doesn't support, you'll have to add them in yourself. The font files are PNG images in the Llanguage folder, which are referenced by a Font.dat text file which contains all the characters in the fonts (in UTF-8). To add a character you just put it at the end of the chars: in Font.dat and then draw them into the font files (both lowercase and uppercase).
Format
Language files are stored in YAML format (UTF-8). Here's a typical language file:
en-US: STR_AVENGER_UFOPEDIA: "TRANSPORTER AND COMBAT SPACECRAFT. THE ULTIMATE REPLICATION OF ALIEN TECHNOLOGY." STR_INTERCEPTOR_UFOPEDIA: "COMBAT AIRCRAFT WITH DUAL PULSE DETONATION ENGINES AND SPECIALLY SHIELDED ELECTRONIC SYSTEMS. THE BEST AVAILABLE EARTH BASED TECHNOLOGY." STR_LIGHTNING_UFOPEDIA: "TRANSPORTER AND COMBAT CRAFT. A CRUDE BUT EFFECTIVE REPLICATION OF ALIEN PROPULSION SYSTEMS." STR_SKYRANGER_UFOPEDIA: "TROOP TRANSPORTER. THE FASTEST OF ITS KIND, WITH VERTICAL TAKE OFF AND LANDING (V.T.O.L.) CAPABILITY." STR_FIRESTORM_UFOPEDIA: "COMBAT CRAFT. THIS ONE-MAN FIGHTER REPLICATES THE CLASSIC ALIEN FLYING SAUCER DESIGN, WITH CENTRAL PROPULSION UNIT." ...
The first line contains the IETF language tag (same as the filename). The rest of the text are just key-string pairs, separated by linebreaks. Language files are placed in the Data\Language folder and have the .yml extension.