Compile PO files into MO (Machine Object) files. MO files are installed on your computer and allow a gettext enabled system to translate the application.
pocompile <po> <mo>
Where:
| <po> | is a standard PO file or directory |
| <mo> | is the output MO (Compiled PO) file or directory |
Options:
| --version | show program’s version number and exit |
| -h, --help | show this help message and exit |
| --manpage | output a manpage based on the help |
| --progress=PROGRESS | show progress as: dots, none, bar, names, verbose |
| --errorlevel=ERRORLEVEL | show errorlevel as: none, message, exception, traceback |
| -iINPUT, --input=INPUT | read from INPUT in po, pot formats |
| -xEXCLUDE, --exclude=EXCLUDE | exclude names matching EXCLUDE from input paths |
| -oOUTPUT, --output=OUTPUT | write to OUTPUT in mo format |
| --psyco=MODE | use psyco to speed up the operation, modes: none, full, profile |
| --fuzzy | use translations marked fuzzy |
| --nofuzzy | don’t use translations marked fuzzy (default) |
pocompile --fuzzy file.po file.mo
Creates a new MO file called file.mo based on the translation in the PO file file.po. By using the --fuzzy option we use all translations including those marked fuzzy.
Gettext plural forms are not handled.