PO Scanner allows the user to localize Portable Object (PO) files. These PO files, also known as catalogs, are available through gettext GNU internationalization library. For more details consult GNU gettext Manual.
The most important settings are the following:
This plug-in is available as a separate plug-in.
Output directory. Specifies the directory where the localized files will be created. This is the directory where Multilizer creates the localized output files and subdirectories. You can specify the name of the localized files and directories by setting Type and Coding.
Type. Specifies how Multilizer names localized files are named and where they are placed. Possible options are:
|Subdirectory||Create localized files in subdirectories named by language and locale.|
|Bundle name||Append the language and locale information to the output file name.|
|File extension||Replace the original file extension with language and locale information.|
Coding. Selects file name initial coding style. Possible values are:
|ISO||ISO standard coding style.|
|.NET||Microsoft .Net coding style.|
|Windows||Windows coding style.|
Native language. Specifies the native language that is used in the target. Set this to match the language in the original file. If the original file contains two or more languages, set the language to the one that is most widely used.
Default language. Specifies the default language. It is the language that is used in the build process, if there is no translation given in the the build language. The translation search order is following: first the build languages, then the default language.
Native encoding. Specifies the native encoding that is used when reading the original file.
Encoding list. Contains the encodings to be used in the localized files. To change the value right click the line and select a new value.
Write BOM. Specifies whether to write Byte Order Mark (BOM) to the localized PO file. By default, BOM characters are written when the output is Unicode. The user can also choose not to write BOM characters at all or write BOM characters only when output is Unicode and the input contains BOM characters as well.
Import Translations from PO file. This setting allows the user to decide whether to import or not to import translations from the original PO file to the current Multilizer project when scanning. By default, the scanner is configured not to import translations. If you get no translations, check that Tools->Options...->Environment->Translations->Allow Scanners overwrite project translations setting is configured correctly.
To language column. Specifies the language project column where to import the translations.
Fill empty translations. Specifies whether to fill empty translation with an empty string or with the native text when building. By default, translations are filled with an empty string.
Scan empty strings. Specifies whether empty strings are scanned.
Context format. Allows the user to choose the format for the rows' context. By default, an index is used as context, but the user can also select the native string or a hash value as context.
When context is Index then the user should ensure that new strings are added only at the end of the existing PO file when being maintained. Otherwise existing context will be broken in Multilizer upon next scan. To prevent this kind of issue the user can choose either Natie string or Hash value as the context format. In this approach, however, all instances of the same native string appear only once in Multilizer project.