#Poedit send in blue how to#
#Poedit send in blue update#
#Poedit send in blue software#
#Poedit send in blue zip#

In that case the developers will add the language to the software or website code using the steps below, then a translator would follow the steps as for updating existing translations with the difference that they would download and translate the latest audacity.pot or audacity_website.pot, change the extension to.

Occasionally a particular language won't yet have a translation, so won't have a. A member of Audacity Team will then commit the file to SVN for future Audacity release (or for the website) and will send a message back to say this has been done. po file(s) and attach to a message to the list.

#Poedit send in blue zip#

Subscribe to the audacity-translation mailing list, zip up the translated. mo file to Audacity.mo, navigate to the 'Languages' folder, open the folder for your language and replace the existing Audacity.mo file with your new one. mo file which in the case of translating the Audacity software you can use to test out your translation in the latest development build. In Poedit, unchanged strings are in black at the bottom of the window. po file, then they haven't changed, and you should be able to ignore them.

If strings are already translated in the.

It should be reviewed against the modified English version and re-translated where necessary. Fuzzy translations are ones where the English has changed slightly, and so the translation has been kept.

Some strings may be marked as 'fuzzy' translations - these show as gold in Poedit.

In Poedit the original strings show as blue at the top of the window.

Untranslated strings obviously need to be translated as normal.

po file loaded into your favourite po-file editor, you can start to translate.

Click OK and wait for Poedit to add the new strings to your.

po file, and the obsolete strings that are in the.

The 'Update summary' will now show lists of the new strings that are in the.

pot file appears in your browser window instead of downloading, right-click over the link and choose 'save target as' or 'save link as'. pot file (the current strings in the source code) for the Audacity software or website. po file for your language (the existing translation) for the Audacity software or website Type any of these commands with only the -help option to learn more, or consult: Poedit To check completeness of a translation against a template file, writing messages to standard error: Or you can omit the output file to write results to standard out. Msgattrib -o out.po -untranslated yourfile.po To see all messages requiring translation, written as a. po file with new strings in it, and the actual translation can be done. Msgmerge -U pt_BR.po audacity_website.pot

#Poedit send in blue update#

Some strings that have slightly changed will be marked up as 'fuzzy' translations, that is the old translation will be kept, but flagged up for a human translator to review later on.įor example to update the pt_BR translation of the Audacity website, you would get the current audacity_website.pot, and run This will result in a re-written yourfile.po with the new strings added. This will update yourfile.po with the new messages for translation from newmessages.pot.

po file, then you can do so using the msgmerge tool from the gettext tools:

If you have the relevant source code, then you can run at the command line: po files for other projects.Ī utility to extract the translatable strings from the source code. KBabel for the KDE desktop environment can also be used to edit. Poedit is a cross-platform editor for the translation files with a wxWidgets-based interface.

#Poedit send in blue how to#

For example, in:įor more detailed instructions to programmers on how to make sure the code you write is easily translatable, see Making Audacity Translatable and Writing Translatable Code. It is best that programmers avoid including such expressions in text for translation, but where such cases exist, leave the function or expression untranslated. Occasionally, code functions or technical expressions with a specific meaning may appear in error messages that require translation. It was to allow us to build Unicode versions of Audacity.Īvoid writing an empty translatable string because they will create problems for gettext. This isn't needed anymore as Unicode is the default. You may see wxT() around the strings in older code. Strings which are not to be translated are written like so: Such strings are detected by the 'xgettext' utility. In the source code, strings which are to be translated are written like so with a preceding underscore: 3.4 Translating and testing the new strings.