You use the Header dialog box to edit the header of the .po file.  The header is a special translation line that has an empty original string.  The header’s translation has a fixed format and is edited by the Header dialog box.  Attempting to edit the header’s translation through the spreadsheet causes the Header dialog box to open automatically.

Certain header values should be changed only by the software maintainer, not by translators.  In order to prevent inadvertent changes, these values are normally read-only.  You must remove the checkmark from the corresponding Locked checkbox to enable editing.

File header comment
This is the block comment at the beginning of the file, above the header translation line.

Statistics
Displays the total number of translation line and also the number of untranslated strings, fuzzy translations and errors.

This is a master PO file
Marks the message catalog as a master PO file.  For more information about master files, refer to “Creating and maintaining a master message catalog” and “Remastering your message catalog”.

Project name and version
This is the name and version of the software application being translated.

Report bugs to
?

POT creation date
The date and time that the .po template was created.  This is normally filled in by the gettext tools used to create the .po file.

PO revision date
The date and time that the .po file was last changed.  This is normally updated by poTree when you save the .po file.

Last translator NAME <EMAIL>
You should set this to your name.  We recommend omitting your email address because it will be included in the .mo file.  Including an email address in any published file is an invitation to receive spam.

Language team NAME <EMAIL>
You should set this to your name or the names of the team members.  We recommend omitting the email address because it will be included in the .mo file.  Including an email address in any published file is an invitation to receive spam.

Charset
The character set used to store the .po file.  We recommend using UTF-8 because it can represent all Unicode characters.  Using a restricted character set such as ISO-8859-1 is not recommended.

Plural forms
Plural forms are currently not supported by poTree.

Format string validation
The type of validation to apply to strings that are marked as format strings.  Select c-format for standard gettext processing or c-format and pf-format for extended format string validation for The Panorama Factory.

Take standard strings from .po file
poTree can read a second .po file that contains standard translations.  For example, The Panorama Factory assumes that wxstd.po is used for standard strings such as OK, Cancel, etc.  When an original matches one in the standard .po file, poTree will show its translation.  If you edit the translation, poTree will add it to the output .mo file as an override.