The Gettext PO format is the standard for WordPress themes and plugins, Drupal modules, Python applications, and GNU software.
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.
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.
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.
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.
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.
“Amazing service! Very professional and quick. Greta communication via WhatsApp and email. I needed my documents very last minute and BeTranslated bent over back to help me with it, delivering hard copy too! Thank you - will use them definitely again in future.”
Google review (SL) , 9 months ago
“It is a real pleasure to work with the BeTranslated team who has been very professional, flexible and responsive during all projects.”
Google review (INTL) , 3 years ago
“Excellent service and good value translation company! Efficient, accurate, and fast turnaround at competitive rates. Highly recommended for their outstanding communication and prompt responses on the chat.”
Google review (SL) , 2 years ago
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.
Send us your Gettext PO file and we will quote as quickly as possible. Format preserved, meaning accurate, delivered on time.
