Difference between revisions of "Translatable"
(new page to explain translatable) |
m (→Explanation) |
||
| Line 1: | Line 1: | ||
| − | + | == Explanation == | |
Items marked with the text {{Translatable}} are WML strings that can be translated. Nearly every string that the player sees can be translated. A program called "gettext" automatically parses your WML files, seeks out strings marked as translatable, and compiles them into a translation template file. Translators can then use this file to create translations of the game into their languages. | Items marked with the text {{Translatable}} are WML strings that can be translated. Nearly every string that the player sees can be translated. A program called "gettext" automatically parses your WML files, seeks out strings marked as translatable, and compiles them into a translation template file. Translators can then use this file to create translations of the game into their languages. | ||
| + | |||
| + | Please hit 'back' on your browser to return to the page you were reading or continue for examples. | ||
You, the scenario writer, must mark a string as translatable by including an underscore character "_" before the string starts. Here is an example. | You, the scenario writer, must mark a string as translatable by including an underscore character "_" before the string starts. Here is an example. | ||
| Line 23: | Line 25: | ||
message=$message_text | message=$message_text | ||
[/message] | [/message] | ||
| + | |||
| + | == See Also == | ||
| + | |||
| + | * [[SyntaxWML]] | ||
Revision as of 18:57, 8 August 2006
Explanation
Items marked with the text (translatable) are WML strings that can be translated. Nearly every string that the player sees can be translated. A program called "gettext" automatically parses your WML files, seeks out strings marked as translatable, and compiles them into a translation template file. Translators can then use this file to create translations of the game into their languages.
Please hit 'back' on your browser to return to the page you were reading or continue for examples.
You, the scenario writer, must mark a string as translatable by including an underscore character "_" before the string starts. Here is an example.
Not translatable: description="Baldras"
Translatable: description= _ "Baldras"
When using strings in macros, include the underscore character with the actual text. Gettext does not know how to perform macro substitution, so always keep the underscore with the string it marks.
Bad:
{VARIABLE message_text ("Hello, fair warrior!")}
[message]
message= _ $message_text
[/message]
Good:
{VARIABLE message_text ( _ "Hello, fair warrior!")}
[message]
message=$message_text
[/message]