Difference between revisions of "Dev:Translation"
m (woops) |
(add gettext manual page) |
||
| Line 1: | Line 1: | ||
= Translating synfig & synfigstudio = | = Translating synfig & synfigstudio = | ||
| − | synfig and synfigstudio are now translatable. We are using the standard gettext system and .po files. When you are building the source, the build system will create a PO Template for both synfig (po/synfig.pot) and synfigstudio (po/synfigstudio.pot). To start a new translation, you can get into the po directory and run msginit, which will determine the correct language code from your environment, ask for your email address and create <languagecode>.po, which you should edit with one of the tools mentioned below. | + | synfig and synfigstudio are now translatable. We are using the standard gettext system and .po files. The [http://www.gnu.org/software/gettext/manual/gettext.html gettext manual] has lots of good advice for translators and programmers alike. When you are building the source, the build system will create a PO Template for both synfig (po/synfig.pot) and synfigstudio (po/synfigstudio.pot). To start a new translation, you can get into the po directory and run msginit, which will determine the correct language code from your environment, ask for your email address and create <languagecode>.po, which you should edit with one of the tools mentioned below. |
We are currently auditing the code for translatable strings, so more strings will appear for translation over time. | We are currently auditing the code for translatable strings, so more strings will appear for translation over time. | ||
Revision as of 15:45, 13 November 2007
Translating synfig & synfigstudio
synfig and synfigstudio are now translatable. We are using the standard gettext system and .po files. The gettext manual has lots of good advice for translators and programmers alike. When you are building the source, the build system will create a PO Template for both synfig (po/synfig.pot) and synfigstudio (po/synfigstudio.pot). To start a new translation, you can get into the po directory and run msginit, which will determine the correct language code from your environment, ask for your email address and create <languagecode>.po, which you should edit with one of the tools mentioned below.
We are currently auditing the code for translatable strings, so more strings will appear for translation over time.
Editing tools
Any text editor (notepad/textedit/gedit/vi/emacs) will do (especially those with specific modes for PO files), but there are a few GUI tools that make the process easier for translators by integrating spell checking, dictionaries and so on:
- KBabel: A KDE/Qt translation tool
- Pootling: A cross-platform tool with some nice features
- gtranslator: a somewhat older tool for GNOME
