UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.10) 
Gecko/20050717 Firefox/1.0.6
IP: 83.129.20.195
URI: http://wesnoth.slack.it/?WescampInstructions
 - - - - -
Index: WescampInstructions
===================================================================
RCS file: /home/wesnoth/cvsroot/wikiroot/WescampInstructions,v
retrieving revision 1.27
diff -u -r1.27 WescampInstructions
--- WescampInstructions 8 Aug 2005 23:42:15 -0000       1.27
+++ WescampInstructions 8 Aug 2005 23:45:06 -0000
@@ -208,9 +208,11 @@
 I change the date and version number for each release, but this must be done 
BEFORE commiting the cfg text files.  You
 should publish immediately after
 getting the new translation.
-There also is a way to include the version number in the desciption without 
breaking the translations:
- description= _ "Year desciption should be written here" + _ " (Version" + " 
1.2.3, 30-2-2005)"
-This way your desciption and ' (Version' are translateable, but the version 
number and date are not.
+HINT: There also is a way to include the version number in the description 
without breaking the translations:
+ description= _ "Your desciption should be written here" + _ " (Version" + " 
1.2.3, 30-2-2005)"
+This way your desciption and ' (Version' are translateable, but the version 
number and date are not. This way your
+description and version become two seperated strings that can be translated 
seperatly. You can now change the version
+number and date as often as you like and you won't break the translations of 
the short description
 
 3. In my example, the only files with translatable text were in the 
./scenarios directory, the ./units directory, and
 Liberty.cfg itself.  YOUR campaign,




_______________________________________________
Wesnoth-wiki-changes mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/wesnoth-wiki-changes

Reply via email to