po4a
Maintain documentation translations via PO files
TLDR
SYNOPSIS
po4a [options] configfile_
DESCRIPTION
po4a (PO for anything) maintains translations of documentation using gettext PO files. It extracts translatable strings from documents, manages PO files, and generates translated versions of documents.The tool supports many documentation formats including man pages, POD, XML, and others. It automates the workflow of keeping translations synchronized with source documents.
PARAMETERS
-f, --force
Force processing even if files are up-to-date.-v, --verbose
Increase verbosity.-q, --quiet
Decrease verbosity.-d, --debug
Output debugging information.--no-translations
Don't generate translated documents, only update POT and PO files.--no-update
Don't update POT and PO files, only generate translations.-k, --keep threshold
Minimum translation percentage to produce output (default: 80).--keep-translations
Keep existing translations even if below threshold.--rm-translations
Remove translated files that fall below threshold.-o, --option opt
Extra options for format plugins.-M, --master-charset charset
Character encoding for source documents.-L, --localized-charset charset
Character encoding for translated documents.--srcdir dir
Base directory for input documents.--destdir dir
Base directory for output documents.--msgmerge-opt options
Additional options passed to msgmerge.-V, --version
Display version and exit.
CAVEATS
Requires format-specific modules. Configuration file defines document mappings. PO files must exist or be created with po4a-gettextize. Complex documents may need manual tweaking.
HISTORY
po4a was created by Martin Quinson to simplify documentation translation using the proven gettext workflow. It enables collaborative translation using standard PO editor tools.
SEE ALSO
po4a-gettextize(1), po4a-translate(1), po4a-updatepo(1), gettext(1), msgfmt(1)
