Revision as of 15:23, 28 June 2007

Quick Navigation

BuildingScenarios

Building scenarios: Advanced

TODO:

This contained a repetition of what was already inside BuildingScenariosIntermediate This should contain:

(more) information about making & using preprocessors (PreprocessorRef)
information on guidelines concerning the general layout of a scenario file
...

Ayone who feels like writing something, go ahead

Mathijs

GetText

As Viliam pointed out (reordered his words):

Translating programs has two steps. The first step is making [...] scenarios that are possible to translate; 
preferably easy to translate. [...] The second step is the translating of the texts... leave this to  translators.

So, as a campaign/scenario developer you have to make sure your campaign will be easy to translate. You can achieve this very easily by preceding all text the user might see on the screen with an underscore. This indicates it is a translatable string. GetText will then be able to look up a translation, based on your localisation settings. To make it ever more clear, here's an example:

.
.
.
[message]
  description=Konrad
  message= _ "I am mighty Konrad! I fought many dummies and now I will fight you!"
[/message]
.
.
.

The message key contains the words that will be displayed when Konrad speaks. So this is a translatable string. So it is preceded with an underscore.

Quick Tag Index

ScenarioWML the top level tags [scenario], [multiplayer], [test], and [tutorial]

EventWML how to describe an event
- FilterWML
- DirectActionsWML, InterfaceActionsWML, InternalActionsWML
SideWML how to describe a side
- SingleUnitWML
- BuildingScenariosShroudData
MapGeneratorWML the random map generator
TimeWML how to describe a day
IntroWML how to describe the intro screen
UtilWML a set of preprocessors you can use

@@ Line 3: / Line 3: @@
 = Building scenarios: Advanced =
-'''TODO:'''
+== '''TODO:''' ==
 This contained a repetition of what was already inside [[BuildingScenariosIntermediate]]
 This should contain:
 * (more) information about making & using preprocessors ([[PreprocessorRef]])
-* information about GetText and making your scenario translatable
 * information on guidelines concerning the general layout of a scenario file
-* LOTS of links to pages any campaign editor needs frequently
 * ...
@@ Line 15: / Line 13: @@
 :Mathijs
+== GetText ==
+As Viliam pointed out (reordered his words):
+ Translating programs has two steps. The first step is making [...] scenarios that are <b>possible</b> to translate;
+ <b>preferably easy</b> to translate. [...] The second step is the translating of the texts... leave this to  translators.
+So, as a campaign/scenario developer you have to make sure your campaign will be easy to translate. You can achieve this very easily by preceding all text the user might see on the screen with an underscore. This indicates it is a translatable string. [[GetText]] will then be able to look up a translation, based on your localisation settings.
+To make it ever more clear, here's an example:
+ .
+ .
+ .
+ [message]
+   description=Konrad
+   message= <b>_</b> "I am mighty Konrad! I fought many dummies and now I will fight you!"
+ [/message]
+ .
+ .
+ .
+The message key contains the words that will be displayed when Konrad speaks. So this is a translatable string. So it is preceded with an underscore.
+== Quick Tag Index ==
+'''[[ScenarioWML]]''' the top level tags [scenario], [multiplayer], [test], and [tutorial]
+:* [[EventWML]] how to describe an event
+:** [[FilterWML]]
+:** [[DirectActionsWML]], [[InterfaceActionsWML]], [[InternalActionsWML]]
+:* [[SideWML]] how to describe a side
+:** [[SingleUnitWML]]
+:** [[BuildingScenariosShroudData]]
+:* [[MapGeneratorWML]] the random map generator
+:* [[TimeWML]] how to describe a day
+:* [[IntroWML]] how to describe the intro screen
+:* [[UtilWML]] a set of preprocessors you can use
 == See Also ==
 * [[ScenarioWML]], [[SyntaxWML]] & [[ReferenceWML]]
 * [[BuildingScenarios]]

Difference between revisions of "BuildingScenariosAdvanced"