“Excellent service and good value translation company. Accurate, fast turnaround at competitive rates. Highly recommended for their outstanding communication and prompt responses.”
Claire C.
Verified Google Review
.po
Gettext PO File Translation for WordPress, Drupal, and Open-Source Software
The Gettext PO format is the standard for WordPress themes and plugins, Drupal modules, Python applications, and GNU software. BeTranslated translates PO and POT files natively, handling plural forms, translator comments, and disambiguation contexts with precision.
Gettext Localization
PO File Translation for CMS and Open-Source Projects
PO files store source strings and their translations alongside metadata: translator comments, extraction comments, and source file references. The format also supports plural form definitions at the file header level and msgctxt disambiguation keys that distinguish identical strings used in different contexts. A translator working in a text editor will often damage PO syntax or ignore these contextual cues.
BeTranslated processes PO files in professional CAT tools that understand the Gettext format natively. Plural form rules for the target language are applied correctly in the Plural-Forms header. Fuzzy-marked strings are reviewed and updated. Msgctxt entries are used to select the contextually correct translation for ambiguous source strings.
What We Handle
.po Translation: Key Capabilities
Plural Form Handling
The Plural-Forms header is updated for the target language and all nplurals values are populated correctly. Complex plural systems in Polish, Russian, and Arabic are handled accurately.
Fuzzy String Review
Strings marked fuzzy in the source PO are reviewed against updated source strings and either confirmed or retranslated. The fuzzy flag is removed from all verified translations in the output.
Msgctxt Disambiguation
Context markers (msgctxt) are used to select the correct translation when the same source string is used in different UI contexts. Context is never ignored.
MO File Compilation
Compiled MO (Machine Object) files for direct use in WordPress or other Gettext-based systems can be generated from the translated PO and delivered alongside the source.
Client Reviews
What Our Clients Say
“The team was meticulous with scientific and academic terminology. They delivered a flawless translation of my doctoral thesis on time, and communication throughout was outstanding.”
Monica Tovar-Vicente
Academic Translation Client
“My experience with BeTranslated was great. They respond quickly and I recommend the agency 100%.”
Adelheid Jaeger
Verified Google Review
Common Questions
.po Translation: Frequently Asked Questions
Everything you need to know about translating Gettext PO files.
A POT (PO Template) file contains only source strings with empty msgstr fields. It is the master template from which language-specific PO files are created. A PO file contains both the source strings and their translations for a specific language. We translate both: POT files produce a new PO file for the target language, and PO files are updated with new or revised translations.
Yes. WordPress plugin and theme localization using PO files is one of the most common requests we receive. We translate the PO file, generate the compiled MO file, and deliver both. If your plugin or theme is on the WordPress.org repository, we are familiar with the naming conventions required for automatic update delivery.
HTML tags inside PO msgstr values (such as bold, links, and line breaks) are preserved and carried through to the translation. Translators are briefed not to translate tag names or attribute values. The delivered PO file contains the same HTML structure as the source with only the text content translated.
Ready to Start
Ready to Translate Your .po Files?
Send us your Gettext PO file and we will quote within one business day. Format preserved, meaning accurate, delivered on time.