Po file editing: Difference between revisions
| (5 intermediate revisions by 2 users not shown) | |||
| Line 27: | Line 27: | ||
Please don't translate variables ( like ${PORT} ). Also check the comment to see if you should should not translate some (like country name has to be in English). | Please don't translate variables ( like ${PORT} ). Also check the comment to see if you should should not translate some (like country name has to be in English). | ||
Note: Don't forget to fill in the header information such as copyright, language team, last translator ... | |||
==PO file Editors== | ==PO file Editors== | ||
| Line 32: | Line 34: | ||
Even though po files are plain text files using an editor designed for po file editing is highly recommended. Most of these tools has advanced features such as format checking, rough translation... | Even though po files are plain text files using an editor designed for po file editing is highly recommended. Most of these tools has advanced features such as format checking, rough translation... | ||
# [http://www.poedit.net/ poedit] | |||
# [http://l10n.kde.org/tools/ Lokalize ] | |||
==Validation== | |||
You can check if there is any obvious mistakes by running the following command | |||
msgfmt -c <file.po> | |||
You will need [http://www.gnu.org/software/gettext/ GNU gettext] package for this command. | |||
Also you can see the details of how many strings translated, how many remains untranslated, how many fuzzy translations are there ... by running the following command | |||
msgfmt --statistics <file.po> | |||
Check your translations against a glossary if one is available for your language. It would ensure a consistent experience (same translation for each word across applications) to the end user. | |||
==Collaboration== | ==Collaboration== | ||