How to Use Poedit
Poedit is a gettext translations editor. This document will show you how to start translating Seven Kingdoms: Ancient Adversaries. It will also discuss some of the features that Poedit has that are useful to translators. For a basic introduction to Poedit, read http://wiki.lxde.org/en/Translate_*.po_files_with_Poedit/. More general information can be found at http://www.icanlocalize.com/site/tutorials/how-to-translate-with-gettext-po-and-pot-files/.
The package name is poedit. Use your distrobution's package manager to install it. Alternatively, you can find the source, a Micro$oft Windows binary, and a MAC OSX binary at http://poedit.net/download.php.
Seven Kingdoms Translation Template
The file is called 7kaa.pot. It is located in ./7kaa/po if you have compiled the source since the Gettext merge.
Opening a file
When starting a new translation, Poedit will prompt you to declare the target language. This will input the language into the header of the translation file. It also sets the puralization rules for that language. Please mention which dialect you speak as this will prevent confusion.
Preferences -- set name and e-mail. This will insert your name and e-mail address into the header of the .po file. This fills the LAST-TRANSLATOR place. You only have to add your name once, and all .po and .pot files you edit henceforth will input you as the last translator. If someone else edits your translation, their name will replace yours and vice versa.
Notes for translators
This is where translation guidelines from the developers appear. It will give contextual information in terms of syntax, semantics, and pragmatics. It will give guidelines regarding character length. It will give guidelines regarding proper nouns and transliteration. It will give guidelines regarding general translation theory. It is not recommended to deviate from these guidelines. Guidelines have been established to ensure consistency among translations and to ease the process; language is language, however.
You can add or edit a comment by clicking on the Comment button. Alternatively, you can configure Poedit to make the comment window editable. Click Edit/Peferences/Editor, and under Behavior, click comment window is editable.
It is a good idea to write comments as you translate the text. The Gettext manual states, "any translation work done seriously will raise many linguistic difficulties, for which decisions have to be made, and the choices further documented. These documents may be saved within the PO file in form of translator comments, which the translator is free to create, delete, or modify at will. These comments may be useful to herself when she returns to this PO file after a while" (Chapter 8. 8.3.10. Pg 60). It is not recommended to erase comments as more documentation is better. This will help other translators working on the same target language and to ensure the translation is high quality. It will also help in writing translation guidelines.
There are a few cases in which translations will be marked fuzzy: original text is changed; the original translator noted something; when another translator does not agree with the original translation, translators should write a comment when he or she marks a translation as fuzzy. Comment: "Marked fuzzy due to..."
After you save the file, Poedit will generate a .po file. Open the .po file you just saved, and add the following header:
# SOME DESCRIPTIVE TITLE. # Copyright (C) 1997, 1998 Enlight Software Ltd. # This file is distributed under the same license as the Seven Kingdoms: Ancient Adversaries package. # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. #
Change the title to $LANGUAGE translation for 7KAA.
If you are the first translator,
- Write your name as the FIRST AUTHOR
- Add your e-mail address
- Input the year in which you created the .po file.
Once the translation is complete, follow the guidelines regarding submitting patches PatchGuidelines
Drepper, Ulrhic, Jim Meyering, Francois Pinard, and Bruno Haible. "GNU Gettext Tools: Native Language Support Library and Tools." 0.18.2. 25 Feb. 2013. http://www.gnu.org/software/gettext/manual/