ilib-loctool-po v1.6.4

ilib-loctool-po

An ilib loctool plugin to parse and localize GNU gettext po files.

This plugin can parse and localize po or pot files written by tools such as easygettext.

Regular PO and POT Files

Entries in a PO file have the following format:

white-space
#  translator-comments
#. extracted-comments
#: reference…
#, flag…
#| msgctxt previous-context
#| msgid previous-untranslated-string
msgctxt context
msgid untranslated-string
msgstr translated-string

The format is specified on the gnu website.

This plugin can read any file with this format. Individual entries are registered at string resources and will appear in the extracted xliff and the new strings files.

If an entry has a context line, it will get a context in the xliff output and will be differentiated from other strings that have the same source but a different (or missing). That is, two entries that differ only by their context will appear as two separate strings in the xliff output.

In POT files, there are often no translations, as it is the "template" that is used to generate all the translated po files. This plugin can support any string with or without translations.

Plurals

This plugin can also support plural strings. Plurals have the following format:

msgid untranslated-string-singular
msgid_plural untranslated-string-plural
msgstr[0] translated-string-case-0
...
msgstr[N] translated-string-case-n

The string in msgid will be considered to be the string for the one category used as the singular in English source. The msgstr_plural will be considered the other category, which is used as the plural string in English. See the Unicode plural categories document for details on what the categories mean.

The lines msgstr[0] through msgstr[N] are the translations of these categories. The numbers are mapped to Unicode categories according to the mappings included below in Appendix A. The mappings are different for each language. That is, in one language, 0 might map to the one category, whereas in another, it might be the zero category. The strings in the xliff output will include the category only, and the categories will be mapped back to numbers in the translated po file output.

Note that for some languages, the number of categories is different than in English. For example, English uses 2 categories (one and other) but Russian uses 3 (one, few, and other). The xliff output will contain the right number of category strings for the target language. Your translators should note the category given in the extype attribute when translating each string. They will not have to add or subtract any xliff trans-unit entries. They only need to translate the contents of the target tag in the given trans-units.

Example

Input po or pot file:

msgid "There is {n} object."
msgstr_plural "There are {n} objects."

Output xliff snippet:

      <trans-unit id="4" resname="There is {n} object." restype="plural" datatype="po" extype="one">
        <source>There is {n} object.</source>
        <target state="new">There is {n} object.</target>
      </trans-unit>
      <trans-unit id="5" resname="There is {n} object." restype="plural" datatype="po" extype="few">
        <source>There are {n} objects.</source>
        <target state="new">There are {n} objects.</target>
      </trans-unit>
      <trans-unit id="6" resname="There is {n} object." restype="plural" datatype="po" extype="other">
        <source>There are {n} objects.</source>
        <target state="new">There are {n} objects.</target>
      </trans-unit>

Note that the msgid string (the English singular) is used as the resource name (resname) for each of the xliff entries so that they can be connected again later when the xliff file is read in. Also, the source string for every category other than one is the source string given on the msgstr_plural line.

Configuring the Plugin

The plugin will look for the po property within the settings of your project.json file. The following setting is used within the po property:

• mappings: a mapping between file matchers and an object that gives info used to localize the files that match it. This allows different po files within the project to be processed into different output files. The matchers are a micromatch-style string, similar to the the includes and excludes section of a project.json file. The value of that mapping is an object that can contain the following properties:
  • template: a path template to use to generate the path to the translated output files. The template replaces strings in square brackets with special values, and keeps any characters intact that are not in square brackets. The default template, if not specified is "dir/locale.po". The plugin recognizes and replaces the following strings in template strings:
    • dir the original directory where the matched source file came from. This is given as a directory that is relative to the root of the project. eg. "foo/bar/strings.po" -> "foo/bar"
    • filename the file name of the matching file. eg. "foo/bar/strings.po" -> "strings.po"
    • basename the basename of the matching file without any extension eg. "foo/bar/strings.po" -> "strings"
    • extension the extension part of the file name of the source file. etc. "foo/bar/strings.po" -> "po"
    • locale the full BCP-47 locale specification for the target locale eg. "zh-Hans-CN" -> "zh-Hans-CN"
    • language the language portion of the full locale eg. "zh-Hans-CN" -> "zh"
    • script the script portion of the full locale eg. "zh-Hans-CN" -> "Hans"
    • region the region portion of the full locale eg. "zh-Hans-CN" -> "CN"
    • localeDir the full locale where each portion of the locale is a directory in this order: langage, script, region. eg, "zh-Hans-CN" -> "zh/Hans/CN", but "en" -> "en".
    • localeUnder the full BCP-47 locale specification, but using underscores to separate the locale parts instead of dashes. eg. "zh-Hans-CN" -> "zh_Hans_CN"
  • localeMap: an output locale map that maps the locale used in the translations to a different locale for use in the file name template. For example, an app may wish to use the locale specifier "zh-CN" instead of the full "zh-Hans-CN" for some output files, but not all of them. In this case, a locale map for this template mapping is how this can be achieved. Any locale not listed in the mapping will be used as-is. The overall shared locale map is also applied if there is no locale map in the template mapping for a particular locale.
  • ignoreComments: specify whether to ignore types of comments. Possible values are:
    • true All comment types should be ignored
    • false No comment types should be ignored (default)
    • Array of strings. Name the types of comments that should be ignored. Possible values are:
      • "translator" - ignore translator comments (prefix is "# ")
      • "extracted" - ignore comments extracted from the source code (prefix is "#.")
      • "flags" - ignore special processing flags (prefix is "#,")
      • "previous" - ignore previous translation (prefix is "#|")
      • "paths" - ignore file names and line numbers (prefix is "#:")
  • headerLocale: specify what kind of locale to put in the file header. Possible values are:
    • full: put the fully specified locale spec in the header
    • abbreviated: put an abbreviated locale spec in the header (language only)
    • mapped: put the results of the output locale mapping (see above) into the header
  • contextInKey: some translation management systems cannot support separate context fields, and therefore two translation units that only differ in their context cannot be distinguished from each other. If this setting is set to "true", then the context is added to the key for a unit. eg. if the string is "Sent" and the context is "Email", a translation unit will be produced with the key "Sent --- Email" and the source string is "Sent".

Example configuration:

{
    "settings": {
        "po": {
            "mappings": {
                "**/template.pot": {
                    "template": "resources/[locale].po",
                    "ignoreComments": ["paths"]
                },
                "sublibrary/**/library.pot": {
                    "template": "[dir]/[locale].po",
                    "localeMap": {
                        "nb-NO": "no",
                        "sr-Cyrl-RS": "sr-RS",
                        "zh-Hans-CN": "zh-CN"
                    },
                    "ignoreComments": true
                }
            }
        }
    }
}

In the above example, any file named template.pot will be localized and the output is sent to a file named after the target locale located in the resources directory. In these files, the translator and extracted type of comments are ignored and will not be extracted into the resources and therefore will not appear in the xliff files.

In the second part of the example, any library.pot file that appears in the sublibrary directory will be localized and the results sent to a po file named after each target locale which will appear in the same directory where the source file was located. If the locale is one of the ones listed in the locale map, it will be mapped before being substituted in to the template. For these files, all comment types are ignored and none are sent to the translators in the xliff files.

If the name of the localized file that the template produces is the same as the source file name, this plugin will throw an exception, the file will not be localized, and the loctool will continue on to the next file.

License

Copyright © 2019, 2022-2023 JEDLSoft

This plugin is license under Apache2. See the LICENSE file for more details.

Release Notes

See CHANGELOG.md

Appendix A. Mappings From GNU gettext Plural Number and Unicode Category

These mappings are encoded in the file pluralforms.json which is packaged with this plugin. The languages are listed below by their ISO 639 2 letter codes. This plugin assumes that any language not explicitly listed below has only the one and other categories.

ar

be

bg

cs

da

de

el

en

eo

es

et

fi

fo

fr

ga

he

hr

hu

id

it

ja

ko

lt

lv

nl

no

pl

pt

ro

ru

sk

sl

sr

sv

th

tr

uk

zh