Difference between revisions of "Dev:Translation"

From Synfig Studio :: Documentation
Jump to: navigation, search
m (add warning on outdated info)
m (Cleaning)
 
(9 intermediate revisions by one other user not shown)
Line 1: Line 1:
−
  '''Warning''' This page contains outdated informations, check the [http://synfig.org/forums forums]
+
{{Title|Translating}}
  
−
= Translating synfig & synfigstudio =
+
= Translating Synfig & Synfig Studio =
  
−
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.
+
We are using the standard {{Literal|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). If those files are missing, run "''make update-po''" in the po/ directories.
+
If you add a .cpp or .h file containing new translatable strings (standard gettext), you must add those files in the associated potfiles.in that you can find in the {{Literal|synfig-core}} or {{Literal|synfig-studio}} po directory.
  
−
== New Translations ==
+
Since the migration to {{Literal|intltool}} the build system does not automatically generate the PO Templates.
−
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.
+
In order to generate and update the translations, from both {{Literal|synfig-core}} and {{Literal|synfig-studio}} directories use the command {{Literal|cd po && make update-po}}.
  
−
== Updating Translations ==
+
= Online translation tool =
−
If you update to a new revision of the code, please run "''make update-po''" in the po/ directories before updating the translation.
+
  
−
We are currently auditing the code for translatable strings, so more strings will appear for translation over time.
+
Synfig can be translated online using an internet browser: https://www.transifex.com/projects/p/synfig
  
−
== Editing tools ==
+
The translation .pot files are automatically pushed from a server to transifex. The .pot files are not pushed immediately, but at a certain time of the day.
  
−
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:
+
== New Translations ==
 +
To start a new translation, use the online translation tool: https://www.transifex.com/projects/p/synfig
  
−
* [http://kbabel.kde.org/ KBabel]: A KDE/Qt translation tool (now discontinued)
+
If you don't have a transifex account, sign up as a contributor, and join the synfig project. Now, you can ask for a new language.
−
* [http://userbase.kde.org/Lokalize Lokalize] The successor of ''KBabel'', for KDE 4.x
+
−
* [http://www.khmeros.info/drupal/?q=en/download/Translation_Editor Pootling]: A cross-platform tool with some nice features
+
−
* [http://sourceforge.net/projects/gtranslator/ gtranslator]: a somewhat older tool for GNOME
+
−
* [http://www.poedit.net/index.php Poedit]: Poedit is cross-platform gettext catalogs (.po files) editor.
+
  
−
== Testing ==
+
== Updating Translations ==
−
 
+
To update the translation, use the online translation tool : https://www.transifex.com/projects/p/synfig
−
To test your translation, save your po file as po/<languagecode>.po, edit configure.ac and add your language code to the ALL_LINGUAS variable (be sure that you are editing the one that is '''before''' AC_OUTPUT rather than adding a new one. Once you have done that, do autoreconf and make install again. Then run synfigstudio or synfig to see how the translations look. If you edit the translation again, you just need to run make install again, no need to autoreconf.
+
−
 
+
−
== Contributing ==
+
−
 
+
−
When your translation is satisfactory or you have an update to it, open a patch in the sf.net bug/patch tracker and we will add it to GIT.
+
−
 
+
−
== Updating to a new translation ==
+
  
−
If you're a regular user you simply follow the build instructions and you'll have a updated version of Synfig.  
+
If you don't have a transifex account, sign up as a contributor, and join synfig project. Now, you can ask to join a language team.
  
−
Otherwise if you are a translator and have tested previously your own translation and have crated a patch that has been added to GIT, you should not update your synfig using your current configure.ac and <languagecode>.po files previously mentioned. If you update with those files currently modified by you you'll obtain a mix of both files (the current one that you have modified/created and the one coming from the last commit). It would produce configuring/building errors. To avoid that simply delete the configure.ac file (it would be restored correctly when git pull) and move, rename or delete the <languagecode>.po file. You'll obtain your own translated file from the current git branch.
+
== More informations about Translations ==
 +
If you need more informations about the synfig translation workflow, you can join the synfig team using the [http://synfig.org/forums forums], or by the [http://sourceforge.net/p/synfig/mailman/synfig-devl/ synfig-devl mailing list]

Latest revision as of 12:49, 9 February 2020

Translating Synfig & Synfig Studio

We are using the standard "gettext" system and .po files. The gettext manual has lots of good advice for translators and programmers alike.

If you add a .cpp or .h file containing new translatable strings (standard gettext), you must add those files in the associated potfiles.in that you can find in the "synfig-core" or "synfig-studio" po directory.

Since the migration to "intltool" the build system does not automatically generate the PO Templates. In order to generate and update the translations, from both "synfig-core" and "synfig-studio" directories use the command "cd po && make update-po".

Online translation tool

Synfig can be translated online using an internet browser: https://www.transifex.com/projects/p/synfig

The translation .pot files are automatically pushed from a server to transifex. The .pot files are not pushed immediately, but at a certain time of the day.

New Translations

To start a new translation, use the online translation tool: https://www.transifex.com/projects/p/synfig

If you don't have a transifex account, sign up as a contributor, and join the synfig project. Now, you can ask for a new language.

Updating Translations

To update the translation, use the online translation tool : https://www.transifex.com/projects/p/synfig

If you don't have a transifex account, sign up as a contributor, and join synfig project. Now, you can ask to join a language team.

More informations about Translations

If you need more informations about the synfig translation workflow, you can join the synfig team using the forums, or by the synfig-devl mailing list

Retrieved from "https://wiki.synfig.org/index.php?title=Dev:Translation&oldid=23386"