Translatable - Revision history

Celtic Minstrel: Fix examples again

2016-08-01T17:38:29Z

Fix examples again

Celtic Minstrel: Correct syntax tags

2016-08-01T17:37:53Z

Correct syntax tags

Celtic Minstrel: /* Explanation */ Correct examples, add syntax highlighting, remove extraneous "how to use your browser"

2016-08-01T17:37:35Z

‎Explanation: Correct examples, add syntax highlighting, remove extraneous "how to use your browser"

Aethaeryn: categorizing

2008-02-24T04:27:24Z

categorizing

Scott: /* Explanation */

2006-08-08T18:58:57Z

‎Explanation

Scott: /* Explanation */

2006-08-08T18:58:11Z

‎Explanation

Scott: /* Explanation */

2006-08-08T18:57:44Z

‎Explanation

Scott: new page to explain translatable

2006-08-08T18:54:07Z

new page to explain translatable

New page

=== 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.

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]

← Older revision		Revision as of 04:27, 24 February 2008
Line 33:		Line 33:

	* [[SyntaxWML]]		* [[SyntaxWML]]
		+
		+	[[Category:Translations]]
		+	[[Category:WML Reference]]

@@ Line 16: / Line 16: @@
 {VARIABLE message_text ("Hello, fair warrior!")}
 [message]
-message= _ {message_text}
+message= _ "$message_text"
 [/message]
 </syntaxhighlight>
@@ Line 24: / Line 24: @@
 {VARIABLE message_text ( _ "Hello, fair warrior!")}
 [message]
-message={message_text}
+message=$message_text
 [/message]
 </syntaxhighlight>

@@ Line 13: / Line 13: @@
 Bad:
-<syntax_highlight lang='wml'>
+<syntaxhighlight lang='wml'>
 {VARIABLE message_text ("Hello, fair warrior!")}
 [message]
@@ Line 21: / Line 21: @@
 Good:
-<syntax_highlight lang='wml'>
+<syntaxhighlight lang='wml'>
 {VARIABLE message_text ( _ "Hello, fair warrior!")}
 [message]

@@ Line 16: / Line 16: @@
   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.
+When using strings in macros, include the underscore character with the actual text. Gettext does not know how to perform macro or variable substitution, so always keep the underscore with the string it marks.
   Bad:

@@ Line 2: / Line 2: @@
 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.