[Wesnoth-wiki-changes] [WesnothWiki] WesnothTranslations

[wiki]

URI http://wesnoth.slack.it/?WesnothTranslations
 - - - - - 
Index: WesnothTranslations
===================================================================
RCS file: /home/wesnoth/cvsroot/wikiroot/WesnothTranslations,v
retrieving revision 1.121
diff -u -r1.121 WesnothTranslations
--- WesnothTranslations 29 Aug 2004 14:46:05 -0000      1.121
+++ WesnothTranslations 30 Aug 2004 14:50:49 -0000
@@ -1,5 +1,6 @@
 || News/Updates ||
 
+August 27 2004 - Wesnoth 0.8.3 released - First official release with gettext 
support <br/>
 August 18 2004 - Added a Spanish translator, David Martínez «ender» <br/>
 August 9 2004 - Added an Italian translator, Giovanni Baldini <br/>
 August 9 2004 - Moved inactive German translators to the "Currently inactive 
translators" section <br/>
@@ -35,11 +36,10 @@
 * <a href="?FinnishCfg">Finnish</a> <br/>
  # paxed - No mail address specified <br/>
 * <a href="?FrenchCfg">French</a> <br/>
- # Guillaume - mailto:gduwelz-rebertDOTcsATclearstreamDOTcom <br/>
  # French speaking mailing list used for translation coordination: 
mailto:address@hidden <br/>
     to subscribe: mailto:address@hidden <br/>
- # DaringTremayne - No mail address specified <br/>
- # Zas - No mail address specified <br/>
+ # French IRC channel dedicated to translation: #wesnoth-fr on irc.wesnothorf 
<br/>
+ # Cedric Duval - mailto:cedricduval+wesnothATfreeDOTfr <br/>
 * <a href="?GermanCfg">German</a> <br/>
  # Christoph Berg - mailto:ChristophDOTBergATkpm-sportDOTde <br/>
  # Michael Vondung - No mail address specified <br/>
@@ -101,6 +101,10 @@
  # ja-el - No mail address specified <br/>
  # Jonas - mailto:celbATgmxDOTat <br/>
  # ammoq - mailto:erichDOTkitzmuellerATchelloDOTat <br/>
+* French <br/>
+ # Guillaume - mailto:gduwelz-rebertDOTcsATclearstreamDOTcom <br/>
+ # DaringTremayne - No mail address specified <br/>
+ # Zas - No mail address specified <br/>
 
 (Please notify me (Skovbaer) if you were wrongfully put on this list ;)
 
@@ -108,6 +112,9 @@
 <hr/>
 || How to submit your translations ||
 
+__Note:__ Skovbaer being currently away (as of late august 2004), the 
coordination is assured by isaac (isaac at
+sindominio dot net) instead. You can send him your translation files.
+
 // || Translation Maintainers || //
 
 The translation maintainers should send the updated/new translation cfg's to 
skovbaer AT femgramskovbaerte DOT dk .
@@ -130,106 +137,32 @@
 <hr/>
 || Translations How-To ||
 
-__If you haven't gotten Wesnoth from latest CVS__, start out by doing so. Take 
a look at WesnothCVS for instructions
+__Notes:__
+* If you haven't gotten Wesnoth from latest CVS, start out by doing so. Take a 
look at WesnothCVS for instructions
 about that.
+* The old translation system, using cfg files and some wesnoth-specific tools 
(make_translation, merge_translation,
+weslang) has been abandoned in the 0.8.3 release of Wesnoth in favor of the 
standard __GNU gettext__ system.
 
-// || Linux instructions - WesLang || //
-
-The easiest method as of May 23 is to use the script 'weslang' to create new 
language cfg's and to keep your language
-cfg up-to-date. The script is fairly simple, it just automates the tasks you 
had to do before. You'll find the script in
-the 'utils' subdirectory, and it has to be run from the Wesnoth topdir (e.g. 
'utils/weslang update french'). Run the
-script with no arguments to get the usage info. <br/>
-Basically new translators should run the command like this:
- utils/weslang make language_name
-Translators who wish to add untranslated strings to a cfg (update it) should 
use:
- utils/weslang update language_name
-Note that you shouldn't put a '.cfg' extension at the end, just type the 
language name ;) <br/>
-
-// || Linux instructions - Manual method || //
-
-From the main Wesnoth directory - run configure with tools option:
-
- ./configure --enable-tools
-
-Then you can simply do:
-
- make
-
-This will compile the game and both make_translation and merge_translations. 
To compile only translation tools, do the
-following:
-
- cd src/tools
- make
-
-To install the tools do:
-
- make install (as root)
-
-If you did this from topdir, you've installed both the game and the tools, if 
you did it from tools dir, you've
-installed translation tools only.
-
-Now that we have the tools, we'll have to build a new translation cfg for your 
language:
-
- make_translation > new.cfg (from topdir)
-
-And then we'll have to merge the current translations for your language (if 
any) with 'new.cfg' and put the new
-contents into another file:
-
- merge_translations data/translations/language.cfg new.cfg > language.cfg
-
-'language' represents the language which you're updating, e.g. 'spanish.cfg'...
-Now move the newly generated 'language.cfg' into it's correct path (probably 
replacing an earlier version of that
-language cfg):
-
- mv -f language.cfg data/translations/
-
-And just remove the file 'new.cfg', you won't need it anymore. Now edit the 
language file with your favorite editor...
-
-// || Windows (and others) instructions || //
+If you are a translator, see GettextForTranslators for more informations.
 
-At the moment we don't have a specific method for Windows users, so just send 
an email to me (Skovbaer) and ask for an
-up-to-date language cfg...
+If you are a developer, gettext internals for Wesnoth are discussed here: 
GettextForWesnothDevelopers.
 
 <hr/>
-|| Editing the language file ||
 
-__If you're making a completely new (non-existant) language cfg__, then things 
should be pretty straightforward.
-Translate all strings between the ""'s. Remember, of course you're not forced 
to go through the cfg from start to
-finish. In fact we'd prefer to receive some work-in-progress versions once in 
a while, so that we can make sure to get
-as much as possible into every new release even though all translations aren't 
finished.
-
-__If you're updating an existing language cfg__, then of course you'll just 
have to translate strings between
- #strings that were not found in the translation,
- #and which should be translated now:
-and
- #---------------------------------
- #strings that have already been translated
-
-That's pretty easy, isn't it? Now get to work! :)
-
-A good tip to all translators is to use defines to keep the skills and such 
constant during diffrent iterations of the
-game.
-
-Do it like this if you want to define a swedish word for backstab for example:
- #define SWEDISH_BACKSTAB
- attack bakifrån
- #enddef
-then later just go...
- weapon_special_backstab="{SWEDISH_BACKSTAB}"
+|| Encoding ||
 
-// __An important thing to remember: Save the cfg in UTF-8 format, if you have 
that possibility ;)__ // <br/>
+// __An important thing to remember: Save the po file in UTF-8 format, if you 
have that possibility ;)__ // <br/>
 Programs such as 'gedit' (Unix, Gnome), 'kwrite' (Unix, KDE), 'TextEdit' or 
'BBEdit' (MacOSX), and Wordpad (Windows)
-among others should be able to save
-in this format (you're welcome to add more editors to this list ;) ). If 
you're not able to save your cfg with UTF8
-formatting, just remember to mention that when you send the cfg to me, and 
then I'll convert it ;) <br/>
+among others should be able to save in this format (you're welcome to add more 
editors to this list ;) ). If you're not
+able to save your po file with UTF8 formatting, just remember to mention that 
when you send the po file to me, and then
+I'll convert it ;) <br/>
 If you have any more questions about this, you can drop me a mail...
 
-Windows users: You can also edit the cfg file in your Windows encoding (using 
Notepad) and convert it from/to UTF8 using
+Windows users: You can also edit the po file in your Windows encoding (using 
Notepad) and convert it from/to UTF8 using
 program "iconv" (available at ftp://xmlsoft.org/win32/).
 
 <hr/>
-|| Switch to gettext ||
 
-An effort has been started to switch from the internationalization mechanism 
of Wesnoth to GNU gettext.
+|| See also ||
 
-See GetText for details.
+* GetText