1. NAME

msgfmt - compile message catalog to binary format

2. SYNOPSIS

msgfmt [OPTION] filename.po ...

3. DESCRIPTION

Generate binary message catalog from textual translation description.

Mandatory arguments to long options are mandatory for short options too. Similarly for optional arguments.

3.1. Input file location:

  • filename.po ...
        input files
  • -D, --directory=DIRECTORY
        add DIRECTORY to list for input files search

If input file is -, standard input is read.

3.2. Operation mode:

  • -j, --java
        Java mode: generate a Java ResourceBundle class
  • --java2
        like --java, and assume Java2 (JDK 1.2 or higher)
  • --csharp
        C# mode: generate a .NET .dll file
  • --csharp-resources
        C# resources mode: generate a .NET .resources file
  • --tcl
        Tcl mode: generate a tcl/msgcat .msg file
  • --qt
        Qt mode: generate a Qt .qm file

3.3. Output file location:

  • -o, --output-file=FILE
        write output to specified file
  • --strict
        enable strict Uniforum mode

If output file is -, output is written to standard output.

3.4. Output file location in Java mode:

  • -r, --resource=RESOURCE
        resource name
  • -l, --locale=LOCALE
        locale name, either language or language_COUNTRY
  • -d DIRECTORY
        base directory of classes directory hierarchy

The class name is determined by appending the locale name to the resource name, separated with an underscore. The -d option is mandatory. The class is written under the specified directory.

3.5. Output file location in C# mode:

  • -r, --resource=RESOURCE
        resource name
  • -l, --locale=LOCALE
        locale name, either language or language_COUNTRY
  • -d DIRECTORY
        base directory for locale dependent .dll files

The -l and -d options are mandatory. The .dll file is written in a subdirectory of the specified directory whose name depends on the locale.

3.6. Output file location in Tcl mode:

  • -l, --locale=LOCALE
        locale name, either language or language_COUNTRY
  • -d DIRECTORY
        base directory of .msg message catalogs

The -l and -d options are mandatory. The .msg file is written in the specified directory.

3.7. Input file syntax:

  • -P, --properties-input
        input files are in Java .properties syntax
  • --stringtable-input
        input files are in NeXTstep/GNUstep .strings syntax

3.8. Input file interpretation:

  • -c, --check
        perform all the checks implied by --check-format, --check-header, --check-domain
  • --check-format
        check language dependent format strings
  • --check-header
        verify presence and contents of the header entry
  • --check-domain
        check for conflicts between domain directives and the --output-file option
  • -C, --check-compatibility
        check that GNU msgfmt behaves like X/Open msgfmt
  • --check-accelerators[=CHAR]
        check presence of keyboard accelerators for menu items
  • -f, --use-fuzzy
        use fuzzy entries in output

3.9. Output details:

  • -a, --alignment=NUMBER
        align strings to NUMBER bytes (default: 1)
  • --no-hash
        binary file will not include the hash table

3.10. Informative output:

  • -h, --help
        display this help and exit
  • -V, --version
        output version information and exit
  • --statistics
        print statistics about translations
  • -v, --verbose
        increase verbosity level

4. AUTHOR

Written by Ulrich Drepper.

5. REPORTING BUGS

Report bugs to < >.

6. COPYRIGHT

Copyright © 1995-1998, 2000-2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.

7. SEE ALSO

The full documentation for

msgfmt is maintained as a Texinfo manual. If the

info and

msgfmt programs are properly installed at your site, the command

info msgfmt

should give you access to the complete manual.