Intlize is intended for use in conjunction with xgettext and msgmerge.
The internationalization process takes four steps.
NAME.pot; where NAME is a unique name for your application.NAME.LANG and the extracted strings from NAME.pot with msgmerge. Or, if NAME.LANG does not exist, copy NAME.pot to NAME.LANG.LANG is the language code, e. g. it for italian or de_AT for german in austria. NAME.pot and NAME.LANG must be in the same directory.NAME.LANG. The intlize runtime framework evaluates the header fields PACKAGE, VERSION and CHARSET. Of course, you want to fill in the missing msgstrs and revise the fuzzy ones.LANG/NAME.msg. The subdirectory LANG is created if necessary.Repeat steps 2 ... 4 for each language. If you are using intlize native format you will need a default translation. To create this default translation, run intlize once with argument -C on one of the NAME.LANG files.
Intlize is invoked with:
intlize [OPTIONS] POFILE
or
intlize -v
POFILE is the edited NAME.LANG file mentioned in the previous chapter.
OPTIONS is one or more of the following:
-kKEYWORD: Search for keyword KEYWORD instead of _
-eENCODING: Store encoding ENCODING instead of the POFILE's CHARSET header field.
Possible values for ENCODING are:
Other values are not yet supported but can be registered on request.
-iVERSIONID: Store the ID VERSIONID instead of the POFILE's PACKAGE and VERSION fields.
-C : (intlize native only) Create a default catalog from the POFILE's msgids in addition to the catalog created from the msgstrs. The default message catalog has the language code C.
-fc : Produce output in catgets format.
-fi : Produce output in intlize native format.
intlize -v prints its version and exits.