The Battle for Wesnoth Wiki - User contributions [en]

User:Friedel

2019-03-10T06:31:38Z

Friedel: fix link

I'm a software developer, computer scientist and software localiser for Afrikaans—a language mainly spoken in South Africa and Namibia.

Have a look at [https://fwolff.net.za/en/ my website] or [https://fwolff.net.za/en/blog/ my blog].

Ek's 'n sagtwareontwikkelaar, rekenaarwetenskaplike en sagtewarelokaliseerder vir Afrikaans.

Kyk gerus na my [https://fwolff.net.za/af/ my webwerf] of [https://fwolff.net.za/af/joernaal/ my webjoernaal].

User:Friedel

2019-03-10T06:24:39Z

Friedel: +Bio

GettextForTranslators

2010-07-22T14:40:58Z

Friedel: /* Tools */ +Virtaal

== Gettext for translators ==

Wesnoth translation is now divided into several text-domains:
* wesnoth
* wesnoth-editor
* wesnoth-lib (contains strings shared by game and editor)
* plus one text-domain for each campaign. The names of these text-domains are constructed from the word wesnoth and the common abbreviation of the campaign (wesnoth-ei, wesnoth-httt, wesnoth-trow, wesnoth-tb, wesnoth-tsg and wesnoth-utbs).

We will use the Swedish (sv) language and the ''wesnoth'' domain as an example in this page.
There are three important files for each text-domain:
* ''wesnoth/wesnoth.pot'' file, which contains all the strings used in the main game (neither editor, nor campaign strings). You can see how a ''.pot'' file looks like in SVN : [http://svn.gna.org/viewcvs/wesnoth/trunk/po/wesnoth/wesnoth.pot?view=markup Current SVN version].
* ''wesnoth/sv.po'', the file containing the translation, you can see how a ''.po'' file looks like in SVN: [http://svn.gna.org/viewcvs/wesnoth/trunk/po/wesnoth/sv.po?view=markup Current SVN version].
* ''{translations_dir}/sv/LC_MESSAGES/wesnoth.gmo'', which is a binary version of <lang>.po that the game will use for efficiency reasons. This is not found in cvs, but is created during compilation of the game.

The first of these files, we update every once in a while, when there is new or modified text,
for instance when a new campaign scenario hits the SVN.

Then, ''msgmerge'' is used to merge this new "state of the game strings" with your current translations, and generate a new, up-to-date, ''sv.po''.

Then, a tool called ''msgfmt'' is called, which generates a new ''wesnoth.gmo'' file from your ''wesnoth.po'' file, which will be used by the game once installed.

"make -C po update-po" does these three steps in one pass.

That was for the "Big Picture".
But you really just need to be concerned with the po file:
translating new strings, checking "fuzzy" entries.
We can handle the administrative tasks of updating etc.
You really don't need to bother with any of these commands, unless you want to compile gmo files to check in-game.

Ivanovic is now responsible for integrating translations into Wesnoth, with the help of Torangan and ott.
You should contact Ivanovic (crazy-ivanovic AT gmx DOT net), and he'll put them in the game.

When sending po files to a maintainer to be included in SVN, please create a zip or tar.gz/bz2 archive that you attach, rather than cutting and pasting the translations into an email. The translated strings are
very sensitive to formatting and the archive will also help distinguish which file is which when sending more than one po file.

== FAQ ==
* What's a fuzzy string?
** It's a string calling for translator revision. For example, if an English string gets a small change and you run the ''msgmerge'' program, it will mark the translation of that string fuzzy. When we switched to gettext we marked all translations as fuzzy as lots of them were outdated.
* What are "Plural-forms"?
** Some languages have different word forms for different numbers of things (for example in English we have "1 thing" but "2 thing'''s'''"). The rules are different for different languages. You can find them [http://translate.sourceforge.net/wiki/l10n/pluralforms here].
* My language needs a different font to get displayed correctly.
** Wesnoth uses several different fonts, and the number is likely to grow with the support for new alphabets/writing systems. Right now we are using DejaVuSans (Roman and Cyrillic), FreeSans (Greek), sazanami-gothic (Japanese) and gkai00mp (Chinese). In the wesnoth/sv.po you will find a string containing the currently used fonts. By changing the order of fonts listed, you choose which font is preferred for your translations. A language using Greek letters would for instance translate that string with:
msgid "DejaVuSans.ttf,FreeSans.ttf,sazanami-gothic.ttf,gkai00mp.ttf"
msgstr "FreeSans.ttf,DejaVuSans.ttf,sazanami-gothic.ttf,gkai00mp.ttf"
Note that if a certain letter/glyph is not found in the first font listed, the second font will be scanned for it and so on.
* What should I do to insert a newline in a string?
** If you want to insert a newline in a string you need to include the pair of characters "". You can use normal newlines as you wish as they don't affect the translation.
* How do I use ' within a single-quote delimited string when translating text= in help screen texts?
** Add a backslash before it.
* What should I do with strings like "Prefs section^General"?
** There are ambiguous strings which should be translated in a different way depending on where they appear. For example, we have "General" in the preferences as "General preferences" and we can also have "a General". These strings can have different translations for a given language, so we use "context" to solve this. The prefix only tries to give a hint about the string, and should be not translated, for example:
msgid "Prefs section^General"
msgstr "General"
* Who can I ask for further information?
** You can ask Ivanovic, Torangan, ott, Yann or Isaac in IRC (irc.freenode.net, #wesnoth or #wesnoth-dev).
If you don't like IRC, send a mail to crazy-ivanovic AT gmx DOT net, or pm him (ivanovic) at the forum.
* How do I quickly test PO file changes?
** When you modify a PO file, run "make update-gmo" in the main po directory to create a new MO file, then run "make install" there to install the new MO file.
** Then force cache rebuild. This is tricky -- if you only update MO files, the game may use a cached (i.e., old) version letting you wonder why it still displays the old translation. Either change game.cfg modification time, e.g. with "touch /usr/local/share/wesnoth/game.cfg", or delete the corresponding cache[s] in ~/.wesnoth/cache.
* The .po file in SVN has changed, how do I move over the translations I've made?
** If your file with additional translations is called old.po and the new file from SVN is called svn.po, create a new file called new.po by doing

msgmerge -o new.po old.po svn.po

The new file new.po will keep your translations from old.po as well as the new strings from svn.po, but check the result -- some translations will not be possible to move across if the original strings changed, these are kept as comments at the end of the file.

* How to generate man files from wesnoth-man(current 1.3 trunk) .po files?
To create "real" manpages out of the po files you have to install a prog
named "po4a" and run make update-po4a inside the maindir before running
make and make install. They are not automatically created out of po
files. With that command the files will be created and afterwards installed.

Note: At least 80% of the .po file must be translated for the creation of a man file

*Why ''svn diff'' is so huge? I have only made a small change to the .po file with poedit.
**When saving .po file poedit unwraps all strings. Usually, all .po files are wrapped at 80 characters so if you want smaller diffs and less merge conflicts you can execute the following commands each time after editing with poedit:

msgattrib file.po > file.po1
mv file.po1 file.po

== Tools ==

There are several tools to work with .po files:
* [http://userbase.kde.org/Lokalize Lokalize] (Unix KDE, intended to replace KBabel)
* [http://i18n.kde.org/tools/kbabel/ KBabel] (Unix KDE)
* [http://gtranslator.sourceforge.net/ GTranslator] (Unix Gnome)
* [http://translate.sourceforge.net/wiki/virtaal/index Virtaal] (Multiplatform)
* [http://www.poedit.net/ poEdit] (Multiplatform)
* [http://www.gnu.org/software/emacs/emacs.html Emacs with po-mode] (Multiplatform)
* [http://www.vim.org/ Vim] with [http://www.vim.org/scripts/script.php?script_id=695 PO plug-in] (Multiplatform)

Of course, you can edit po files with any UTF-8 capable text editor, but the tools listed above have great advantages over any text editor regarding .po translation, like going to next fuzzy/untranslated string, searching only in specific fields (msgid, msgstr, comment), ...

== See Also ==

* [[WesnothTranslations]]
* [[WesnothTranslationsHowTo]]
* [[GettextForWesnothDevelopers]]
* [http://gettext.wesnoth.org/ Translation statistics]

[[Category:Translations]]

WesnothTranslationsHowTo

2007-06-08T11:25:23Z

Friedel: /* How to submit your translations */ Mention the preferred submittion format maintainters should use

This page contains information on how-to translate and submit translation updates.

== How to submit your translations ==

'' ''' Translation Maintainers ''' ''

The translation maintainers should send the updated/new translation
po-files to the language coordinator:
Ivanovic (crazy-ivanovic AT gmx DOT net) or
Torangan (david AT torangan DOT de).
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 SVN (the online source code repository). You should also subscribe to the [http://www.wesnoth.org/wiki/WesnothTranslations#Mailing_List wesnoth-i18n mailinglist].

Send the files as an archive containing the complete .po files (no .mo or .gmo files) and ensure that they follow the directory structure used in version control. For example, the archive with the German (de) translations should therefore be structured as follows:
wesnoth/de.po
wesnoth-httt/de.po
wesnoth-tutorial/de.po
etc.

'' ''' Translators ''' ''

The other translators (those who are not maintainers) should contact
the maintainer for their language to see if there is some work to do.
After you have done some work on the translation you should email it
to your language maintainer. He/she will then (if needed) check it over
before sending it on to the language coordinators. A list of all translators
currently working on a language is found on each language page.

'' ''' NEW Translators ''' ''

If you want to help out with the translation of an language already started on,
contact the translation maintainer for the language.
If you want to start translation of Wesnoth to a new language,
first contact Ivanovic or Torangan.
And then just follow the instructions written in '' Translators '' .

== Translations How-To ==

Notes:
* If you haven't got Wesnoth from latest SVN, start out by doing so.
Take a look at [[WesnothSVN]] for instructions about that.
* The old translation system, using cfg files and some wesnoth-specific
tools (make_translation, merge_translation, weslang) was abandoned
in the 0.8.3 release of Wesnoth in favor of the standard __GNU gettext__ system.
* Infos how the two branches do work can be found in the [http://www.wesnoth.org/forum/viewtopic.php?t=7618 Forum].

If you are a translator, see [[GettextForTranslators]] for more information.

If you are a developer, gettext internals for Wesnoth are discussed here:
[[GettextForWesnothDevelopers]].

== Specifying typefaces and fonts for a translation ==

Translations in a language which mainly uses characters outside of the Latin1 character set may want to specify different typefaces. In the translatable strings, there is a string named
"DejaVuSans.ttf,FreeSans.ttf,sazanami-gothic.ttf,gkai00mp.ttf"
which specifies the order in which fonts are to be tried, for each character, before the program finds a font which contains this character: the font appearing first in the list is tried first. Translators may change this string in the translation.
For example, it would be a good idea to specify first a font which contains all the characters generally used in the target language. This is especially important for translations into Asian languages. Please refer to the page [[WesnothAsianLanguages]] for more information.

== See Also ==
* [[GettextForTranslators]]
* [[WesnothAsianLanguages]]
* [[WesnothTranslations]]
* [[TranslatorsGuide]]
* [http://gettext.wesnoth.org Translation statistics]

WesnothTranslations

2007-06-08T07:45:37Z

Friedel: /* Translations */ New Afrikaans maintainer

== Translations ==

Wesnoth is currently being translated into the following languages. Instructions on how to contribute are found here:
[[WesnothTranslationsHowTo]].
* [[AfrikaansTranslation|Afrikaans]] - maintainer: Friedel Wolff - [mailto:friedelATSIGNtranslateDOTorgDOTza]
* [[BasqueTranslation|Basque]] - maintainer: Alfredo Beaumont (ziberpunk) - [mailto:alfredo.beaumontATgmailDOTcom]
* [[BulgarianTranslation|Bulgarian]] maintainer: Nikolay Vladimirov (Turki) - [mailto:nikolayATvladimiroffDOTcom]
* [[CatalanTranslation|Catalan]] - maintainer: Jordà Polo (ettin) - [mailto:jordaATettinDOTorg]
* [[ChineseTranslation|Chinese]] - maintainer: Firen, [mailto:qhy@hotmail.co.uk] (email address not working)
* [[CzechTranslation|Czech]] - maintainer: Vladimír Slávik - [mailto:slavikDOTvladimirATseznamDOTcz]
* [[DanishTranslation|Danish]] maintainer: Joe Hansen (joedalton) - [mailto:joedalton2ATyahooDOTdk]
* [[DutchTranslation|Dutch]] - maintainer: Foppe Benedictus (Fopper) - [mailto:foppeDOTbenedictusATgmailDOTcom]
* [[EnglishTranslation|English (US)]] ''(this is the default)'' - maintainer: Sirp - [mailto:davidnwhiteATcomcastDOTnet]
* [[EnglishGBTranslation|English (GB)]] - maintainer: pjr - [mailto:peadar.ruadh@btinternet.com]
* [[Esperanto_translation|Esperanto]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]
* [[EstonianTranslation|Estonian]] - maintainer: Mart Tõnso (rinjin) - [mailto:tmATrinjinDOTpriDOTee]
* [[FilipinoTranslation|Filipino]] - maintainer: Joset Zamora (sophie^) - [mailto:sophieUNDERSCOREgeekATyahooDOTca]
* [[FinnishTranslation|Finnish]] - maintainer: Jussi Rautio (jgrr) - [mailto:jussiDOTrautioAThutDOTfi]
* [[FrenchTranslation|French]] - maintainer: Benoît Timbert (Noyga) [mailto:benoitDOTtimbertATfreeDOTfr] (interim) or: Guillaume Massart (Piou2fois) - [mailto:massartDOTguillaumeATwanadooDOTfr] (currently away)
* [[GalicianTranslation|Galician]] - maintainer: Jacobo Fernandez (Xakobe) - [mailto:xakobe_gzAThotmailDOTcom] (email address not working)
* [[GermanTranslation|German]] - maintainer: Christoph Berg (chrber) - [mailto:ChristophDOTBergATkpm-sportDOTde]
* [[GreekTranslation|Greek]] - maintainer: Konstantinos Egarhos [mailto:atixosATgmailDOTcom]
* [[HebrewTranslation|Hebrew]] - maintainer: Oron Peled - [mailto:oronATactcomDOTcoDOTil]
* [[HungarianTranslation|Hungarian]] - maintainer: Széll Tamás (TomJoad) - [mailto:tomiATdigiflexDOThu]
* [[IndonesianTranslation|Indonesian]] - maintainer: Nicky Inkrais Witras [mailto:nickyATsefierDOTcom]
* [[ItalianTranslation|Italian]] - maintainer: Luciano Montanaro - [mailto:mikelima@cirulla.net]
* [[JapaneseTranslation|Japanese]] - maintainer: Nobuhito Okada - [mailto:okyadaATgmailDOTcom]
* [[KoreanTranslation|Korean]] - maintainer: Kim Woong - [mailto:jojowarezAThotmailDOTcom] (email address not working)
* [[LatinTranslation|Latin]] - maintainer: Marc Polo ([http://www.wesnoth.org/forum/privmsg.php?mode=post&u=571 mpolo]) - No mail address specified
* [[NorwegianTranslation|Norwegian]] - maintainer: Gaute Jao (Gauteamus) - [mailto:gauteamusATgmailDOTcom] or: Asgeir Aakre [mailto:asgeiraakre@gmail.com]
* [[OccitanTranslation|Occitan]] - maintainer: Nobody, currently
* [[PolishTranslation|Polish]] - maintainer: Zbigniew Banach - [mailto:zDOTbanachATwsisizDOTeduDOTpl]
* [[PortugueseTranslation|Portuguese Brazilian]] - maintainer: Claus Aranha (caranha) - [mailto:caranhaATgmailDOTcom]
* [[RussianTranslation|Russian]] - maintainer: Azamat H. Hackimov [mailto:azamatDOThackimovATgmailDOTcom]
* [[SerbianTranslation|Serbian]] - maintainer: Srećko Toroman (freecraft)- [mailto:sreckotoromanATgmailDOTcom]
* [[(sk) Preklad|Slovak]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]; wiki: [[(sk) Návod]]
* [[SlovenianTranslation|Slovenian]] - maintainer: Jaka Kranjc (lynx) - [mailto:lynxlupodianAThotmailDOTcom]
* [[SpanishTranslation|Spanish]] - maintainer: Roberto Romero [mailto:sildurinENgmail.com]
* [[SwedishTranslation|Swedish]] - maintainer: Stefan Bergström (tephlon) - [mailto:stefanDOTbergstromATgmailDOTcom]
* [[TurkishTranslation|Turkish]] - maintainer: Pınar Yanardağ (PINguAR) - [mailto:pinarATcomuDOTeduDOTtr]
* [[ValencianTranslation|Valencian]] - maintainer: Mario (Mavorte) - [mailto:mavorte1ATyahooDOTes]; wiki: [[MavorteValencia]]
* [[VietnameseTranslation|Vietnamese]] - maintainer: Do Hong Minh - [mailto:minhdhAThutticDOTcom]

Other ideas (remember, these are just ideas):
* Translations into Asian languages
** Asian languages are already supported. See [[WesnothAsianLanguages]].

== Mailing List ==

There now is a mailinglist dedicated to translation matters. It is mainly intended to be used for informing translation maintainers about important changes, to announce string freezes and other special things. Everyone is free to subscribe to this list. You can find this list, entitled wesnoth-i18n at the listing of all Wesnoth mailing lists:

[http://gna.org/mail/?group=wesnoth http://gna.org/mail/?group=wesnoth]

The archive for this list is to be found [http://mail.gna.org/public/wesnoth-i18n/ here].
Please keep in mind that this list is not meant for discussing changes for one single translation but stuff that is relevant to all translations.

== See also ==

* [[WesnothTranslationsHowTo]]
* [[GetText]]
* [http://gettext.wesnoth.org Translations statistics (svn)]
* [[WesCamp| Translating User made Campaigns (featuring WesCamp-i18n)]]