UserAgent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/312.1 (KHTML, like Gecko) Safari/312 IP: 65.37.49.4 URI: http://wesnoth.slack.it/?WescampInstructions - - - - - Index: WescampInstructions =================================================================== RCS file: /home/wesnoth/cvsroot/wikiroot/WescampInstructions,v retrieving revision 1.6 diff -u -r1.6 WescampInstructions --- WescampInstructions 3 Jun 2005 16:13:44 -0000 1.6 +++ WescampInstructions 3 Jun 2005 16:44:25 -0000 @@ -5,6 +5,9 @@ not require a tremendous amount of technical knowledge from user campaign writers. However, some familiarity with the terminal and command line is required. This guide was written by a Mac OS X user, so hopefully it will be explicit enough for anybody. +In a user campaign, the scenario cfg files, some custom units, //campaignname//.cfg, and some macros contain translatable text. You will be shown how +to send those files to the wescamp project on www.berlios.de and how to download the completed translation files. + ||Preliminary Steps|| 1. You must register yourself at http://www.berlios.de which is like a German version of Sourceforge. Remember your password because you're going to @@ -95,7 +98,44 @@ ||Updating your Translations|| +A similar process is used to download updated translations and move the files over to your campaign folder. Here is a shell script to do the job. Call it +something simple, like 'get' and save it in the /data/campaigns directory. + #!/bin/csh -f + + set libpath = '~/Library/Preferences/Wesnoth/data/campaigns/Liberty' + set wescamp = '~/Library/Preferences/Wesnoth/data/campaigns/Liberty-po' + + echo checking out latest translation... + cd $wescamp + svn checkout svn+ssh://svn.berlios.de/svnroot/repos/wescamp-i18n/Liberty-po/Liberty/translations + + echo copying translation files into campaign folder... + cp -Rf $wescamp/Liberty/translations/* $libpath/translations/ + + echo finished. + +You will again be asked for your berlios.de password one or more times (3 for me). Technically you don't need to send the secure version of the command +(there's an anonymous checkout command you could use), but this will make sure you have write access for the whole tree and is more consistent with +everything else you have been doing. + +||Summary|| + +This page showed you how to set up a wescamp/SVN repository on your local computer. A method was presented for pulling translations down from +wescamp and sending your updated text files to wescamp. Other methods exist that use your campaign folder as the local SVN repository, but this is how I +do it. + +Here are some final notes. + +1. Once you send your updated cfg files to wescamp, contact the translation team via torangan. They may get automatic commit notifications from +www.berlios.de, but you will ensure they don't miss your campaign. + +2. After you commit the updated cfg files, DO NOT CHANGE A SINGLE CHARACTER of your text strings. Doing so invalidates the translation for that string. +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. +3. In my example, the only files with translatable text were in the ./scenarios directory, the ./units directory, and Liberty.cfg itself. YOUR campaign, +especially if you use the template by Invisible Philosopher, may have other files that contain translatable text like a utils.cfg or deaths.cfg file. You should +adapt the process to commit ALL files that contain translatable text. ||See Also||
_______________________________________________ Wesnoth-wiki-changes mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/wesnoth-wiki-changes
