[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.123
diff -u -r1.123 WesnothTranslations
--- WesnothTranslations 30 Aug 2004 14:51:48 -0000      1.123
+++ WesnothTranslations 30 Aug 2004 14:53:11 -0000
@@ -117,7 +117,7 @@
 
 // || Translation Maintainers || //
 
-The translation maintainers should send the updated/new translation cfg's to 
skovbaer AT femgramskovbaerte DOT dk .
+The translation maintainers should send the updated/new translation po's to 
skovbaer AT femgramskovbaerte DOT dk .
 Additionally they have to quickly check over other people's translations 
(other people translating the same language)
 as the other translators (if any) will have to send their translations to 
their language maintainer before inclusion
 in the CVS (the online source code repository).
@@ -138,28 +138,14 @@
 || Translations How-To ||
 
 __Notes:__
-* If you haven't gotten Wesnoth from latest CVS, start out by doing so. Take a 
look at WesnothCVS for instructions
+* If you haven't got 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.
 
-If you are a translator, see GettextForTranslators for more informations.
+If you are a translator, see GettextForTranslators for more information.
 
 If you are a developer, gettext internals for Wesnoth are discussed here: 
GettextForWesnothDevelopers.
-
-<hr/>
-
-|| Encoding ||
-
-// __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 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 po file in your Windows encoding (using 
Notepad) and convert it from/to UTF8 using
-program "iconv" (available at ftp://xmlsoft.org/win32/).
 
 <hr/>