PO file with GNU gettext format
Many applications use Portable Object (PO) files mainly for storing translations of the user interface (UI). Each language has its own PO file. The file format used most is GNU gettext. Each PO file contains entries with the source text, which serves as a reference in the code, and the target text, which is actually shown to the user.
#: input/leanback-resources.js:loginTitle msgctxt "leanback" msgid "Please login" msgstr "Bitte anmelden um Ihren Account zu sehen" #: input/leanback-resources.js:username #, fuzzy msgctxt "leanback" msgid "Username:" msgstr "Email:" #: input/leanback-resources.js:password msgctxt "leanback" msgid "Password:" msgstr "Passwort:"
The text in the code is often written by the programmer who created it. The source text may then be in “programmer” English and is usually replaced in the UI by the target text of an English PO file. This means the source text is sometimes a poor basis for a translation.
#: input/leanback-resources.js:loginTitle msgctxt "leanback" msgid "Please login" msgstr "Please login to see your account" #: input/leanback-resources.js:username #, fuzzy msgctxt "leanback" msgid "Username:" msgstr "Email:" #: input/leanback-resources.js:password msgctxt "leanback" msgid "Password:" msgstr "Password:"
Alternatively, you could simply prefer to use a different language than the source language as a basis for translation. For example, use the German text instead of the English.
Translating using Trados Studio
In Trados Studio, you will get the PO source and target text when preparing the file with the built-in PO file type definition.
If the source text is not a good basis, you will probably use the target text and replace it with your translation. This makes it harder to proofread the translation since the text which was used for translation is gone. You will have to use the original PO file in order to have a look at the original target text.
With our plugin, it is possible to specify whether the PO target text should be shown as the source text in Trados Studio and thus be used as the basis for your translation. For example, if you have a PO file with English as the source and German as the target, you can create a translation into French using the German text and generate a translated PO file with English as source and French as target without having to convert any PO files. This can also be applied to PO files with “programmer” English as the source and corrected English as the target.
Show PO target text as source
It is also possible to define whether the target text of the PO file should be added to the target segments in Trados or not.
Add PO target text (like built-in PO file type definition)
Do not add PO target text
With these settings you won’t need to convert any PO files anymore and surely won’t have to remove or replace any texts in target segments.
The plugin supports embedded content replacement with tags. The default settings already contain common placeholders and tag pairs for HTML.
If you click on the field structure information next to the segment, you will get information about the location of the entry and the entry’s message context if applicable.
Download and installation
Download the plugin here and double click on the .sdlplugin file to start the plugin installer.