266
edits
Changes
Jump to navigation
Jump to search
Line 187:
Line 187: + + + + + + + + + + Line 206:
Line 216: − +
Development Team/Almanac/Internationalization (view source)
Revision as of 07:33, 17 July 2012
, 07:33, 17 July 2012→Step 4: Use msginit to generate a .po file
Notice that the "msgstr" lines are empty. This is where translations go, as we shall discuss next.
Notice that the "msgstr" lines are empty. This is where translations go, as we shall discuss next.
=== Step 4.5: Use msgmerge to merge an existent .po file ===
If you want to update an existent .po file already generated by someone else, you should use ''msgmerge'' instead of ''msginit''. This is useful to update the existent es.po file, for example, to add new strings to be translated and preserve those ones that are already translated.
So, to do this, you should run:
msgmerge -o <output-file> <file-to-be-updated> <pot-file>
And then edit ''output-file'' to translate the new strings added.
=== Step 5: Translate all the strings that need translation. ===
=== Step 5: Translate all the strings that need translation. ===
</pre>
</pre>
A better way is to plug in to the Pootle system that employs translators from all different languages. Visit the [https://dev.laptop.org/translate/ One Laptop Per Child: Translation System] to find out more about using Pootle and putting your activity's po files up for translation.
A better way is to plug in to the Pootle system that employs translators from all different languages. Visit the [http://translate.sugarlabs.org SugarLabs: Translation System] to find out more about using Pootle and putting your activity's po files up for translation.
=== Step 6: Generate a ".mo" file using msgfmt and install the translation in to your activity by putting the .mo file in the locale/LANG/LC_MESSAGES directory. ===
=== Step 6: Generate a ".mo" file using msgfmt and install the translation in to your activity by putting the .mo file in the locale/LANG/LC_MESSAGES directory. ===