Gettext PO (Portable Object) file

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Add details about Gettext PO files)
 
 
(One intermediate revision by one user not shown)
Line 1: Line 1:
 +
{{FormatInfo
 +
|formattype=electronic
 +
|subcat=Resources
 +
|extensions={{ext|po}}
 +
}}
 
From the manpage the gettext program translates a natural language message into the user's language, by looking up the translation in a message catalog.
 
From the manpage the gettext program translates a natural language message into the user's language, by looking up the translation in a message catalog.
  
Line 21: Line 26:
 
== Additional links ==
 
== Additional links ==
  
 +
* [https://www.gnu.org/software/gettext/ Gettext project page]
 
* [https://www.labri.fr/perso/fleury/posts/programming/a-quick-gettext-tutorial.html A Quick Gettext Tutorial]
 
* [https://www.labri.fr/perso/fleury/posts/programming/a-quick-gettext-tutorial.html A Quick Gettext Tutorial]

Latest revision as of 00:19, 18 March 2021

File Format
Name Gettext PO (Portable Object) file
Ontology
Extension(s) .po

From the manpage the gettext program translates a natural language message into the user's language, by looking up the translation in a message catalog.

A Gettext PO file is one of two Gettext file types conveying translations in source code. The PO file contains human readable and editable text with a single target translation and linked to plain-text strings in source code. The second file, a Gettext MO (Machine Object) file is a compiled binary representation of the same data for use in the calling application. The MO file is generated from the PO source, usually in a batch workflow for a single project.

Contents

[edit] File structure

The file structure of a PO file is described in the Gettext documentation.

[edit] Example PO files

[edit] References

[edit] Additional links

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox