msgattrib [option] [inputfile]
msgattrib program filters the messages of a translation catalog
according to their attributes, and manipulates the attributes.
Input PO file.
Add directory to the list of directories. Source files are searched relative to this list of directories. The resulting .po file will be written relative to the current directory, though.
If no inputfile is given or if it is ‘-’, standard input is read.
Write output to specified file.
The results are written to standard output if no output file is specified or if it is ‘-’.
Keep translated messages, remove untranslated messages.
Keep untranslated messages, remove translated messages.
Remove ‘fuzzy’ marked messages.
Keep ‘fuzzy’ marked messages, remove all other messages.
Remove obsolete #~ messages.
Keep obsolete #~ messages, remove all other messages.
Attributes are modified after the message selection/removal has been performed. If the ‘--only-file’ or ‘--ignore-file’ option is specified, the attribute modification is applied only to those messages that are listed in the only-file and not listed in the ignore-file.
Set all messages ‘fuzzy’.
Set all messages non-‘fuzzy’.
Set all messages obsolete.
Set all messages non-obsolete.
When setting ‘fuzzy’ mark, keep “previous msgid” of translated messages.
Remove the “previous msgid” (‘#|’) comments from all messages.
When removing ‘fuzzy’ mark, also set msgstr empty.
Limit the attribute changes to entries that are listed in file. file should be a PO or POT file.
Limit the attribute changes to entries that are not listed in file. file should be a PO or POT file.
Synonym for ‘--only-fuzzy --clear-fuzzy’: It keeps only the fuzzy messages and removes their ‘fuzzy’ mark.
Synonym for ‘--only-obsolete --clear-obsolete’: It keeps only the obsolete messages and makes them non-obsolete.
Specify whether or when to use colors and other text attributes.
--color option for details.
Specify the CSS style rule file to use for
--style option for details.
Always write an output file even if it contains no message.
Write the .po file using indented style.
Do not write ‘#: filename:line’ lines.
Generate ‘#: filename:line’ lines (default).
The optional type can be either ‘full’, ‘file’, or
‘never’. If it is not given or ‘full’, it generates the
lines with both file name and line number. If it is ‘file’, the
line number part is omitted. If it is ‘never’, it completely
suppresses the lines (same as
Write out a strict Uniforum conforming PO file. Note that this Uniforum format should be avoided because it doesn’t support the GNU extensions.
Write out a Java ResourceBundle in Java
.properties syntax. Note
that this file format doesn’t support plural forms and silently drops
Write out a NeXTstep/GNUstep localized resource file in
Note that this file format doesn’t support plural forms.
Set the output page width. Long strings in the output files will be split across multiple lines in order to ensure that each line’s width (= number of screen columns) is less or equal to the given number.
Do not break long message lines. Message lines whose width exceeds the output page width will not be split into several lines. Only file reference lines which are wider than the output page width will be split.
Generate sorted output. Note that using this option makes it much harder for the translator to understand each message’s context.
Sort output by file location.