1@pindex msguniq 2@cindex @code{msguniq} program, usage 3@example 4msguniq [@var{option}] [@var{inputfile}] 5@end example 6 7@cindex unify duplicate translations 8@cindex duplicate removal 9The @code{msguniq} program unifies duplicate translations in a translation 10catalog. It finds duplicate translations of the same message ID. Such 11duplicates are invalid input for other programs like @code{msgfmt}, 12@code{msgmerge} or @code{msgcat}. By default, duplicates are merged 13together. When using the @samp{--repeated} option, only duplicates are 14output, and all other messages are discarded. Comments and extracted 15comments will be cumulated, except that if @samp{--use-first} is 16specified, they will be taken from the first translation. File positions 17will be cumulated. When using the @samp{--unique} option, duplicates are 18discarded. 19 20@subsection Input file location 21 22@table @samp 23@item @var{inputfile} 24Input PO file. 25 26@item -D @var{directory} 27@itemx --directory=@var{directory} 28@opindex -D@r{, @code{msguniq} option} 29@opindex --directory@r{, @code{msguniq} option} 30Add @var{directory} to the list of directories. Source files are 31searched relative to this list of directories. The resulting @file{.po} 32file will be written relative to the current directory, though. 33 34@end table 35 36If no @var{inputfile} is given or if it is @samp{-}, standard input is read. 37 38@subsection Output file location 39 40@table @samp 41@item -o @var{file} 42@itemx --output-file=@var{file} 43@opindex -o@r{, @code{msguniq} option} 44@opindex --output-file@r{, @code{msguniq} option} 45Write output to specified file. 46 47@end table 48 49The results are written to standard output if no output file is specified 50or if it is @samp{-}. 51 52@subsection Message selection 53 54@table @samp 55@item -d 56@itemx --repeated 57@opindex -d@r{, @code{msguniq} option} 58@opindex --repeated@r{, @code{msguniq} option} 59Print only duplicates. 60 61@item -u 62@itemx --unique 63@opindex -u@r{, @code{msguniq} option} 64@opindex --unique@r{, @code{msguniq} option} 65Print only unique messages, discard duplicates. 66 67@end table 68 69@subsection Input file syntax 70 71@table @samp 72@item -P 73@itemx --properties-input 74@opindex -P@r{, @code{msguniq} option} 75@opindex --properties-input@r{, @code{msguniq} option} 76Assume the input file is a Java ResourceBundle in Java @code{.properties} 77syntax, not in PO file syntax. 78 79@item --stringtable-input 80@opindex --stringtable-input@r{, @code{msguniq} option} 81Assume the input file is a NeXTstep/GNUstep localized resource file in 82@code{.strings} syntax, not in PO file syntax. 83 84@end table 85 86@subsection Output details 87 88@c --no-escape and --escape omitted on purpose. They are not useful. 89 90@table @samp 91@item -t 92@itemx --to-code=@var{name} 93@opindex -t@r{, @code{msguniq} option} 94@opindex --to-code@r{, @code{msguniq} option} 95Specify encoding for output. 96 97@item --use-first 98@opindex --use-first@r{, @code{msguniq} option} 99Use first available translation for each message. Don't merge several 100translations into one. 101 102@item --force-po 103@opindex --force-po@r{, @code{msguniq} option} 104Always write an output file even if it contains no message. 105 106@item -i 107@itemx --indent 108@opindex -i@r{, @code{msguniq} option} 109@opindex --indent@r{, @code{msguniq} option} 110Write the .po file using indented style. 111 112@item --no-location 113@opindex --no-location@r{, @code{msguniq} option} 114Do not write @samp{#: @var{filename}:@var{line}} lines. 115 116@item -n 117@itemx --add-location 118@opindex -n@r{, @code{msguniq} option} 119@opindex --add-location@r{, @code{msguniq} option} 120Generate @samp{#: @var{filename}:@var{line}} lines (default). 121 122@item --strict 123@opindex --strict@r{, @code{msguniq} option} 124Write out a strict Uniforum conforming PO file. Note that this 125Uniforum format should be avoided because it doesn't support the 126GNU extensions. 127 128@item -p 129@itemx --properties-output 130@opindex -p@r{, @code{msguniq} option} 131@opindex --properties-output@r{, @code{msguniq} option} 132Write out a Java ResourceBundle in Java @code{.properties} syntax. Note 133that this file format doesn't support plural forms and silently drops 134obsolete messages. 135 136@item --stringtable-output 137@opindex --stringtable-output@r{, @code{msguniq} option} 138Write out a NeXTstep/GNUstep localized resource file in @code{.strings} syntax. 139Note that this file format doesn't support plural forms. 140 141@item -w @var{number} 142@itemx --width=@var{number} 143@opindex -w@r{, @code{msguniq} option} 144@opindex --width@r{, @code{msguniq} option} 145Set the output page width. Long strings in the output files will be 146split across multiple lines in order to ensure that each line's width 147(= number of screen columns) is less or equal to the given @var{number}. 148 149@item --no-wrap 150@opindex --no-wrap@r{, @code{msguniq} option} 151Do not break long message lines. Message lines whose width exceeds the 152output page width will not be split into several lines. Only file reference 153lines which are wider than the output page width will be split. 154 155@item -s 156@itemx --sort-output 157@opindex -s@r{, @code{msguniq} option} 158@opindex --sort-output@r{, @code{msguniq} option} 159Generate sorted output. Note that using this option makes it much harder 160for the translator to understand each message's context. 161 162@item -F 163@itemx --sort-by-file 164@opindex -F@r{, @code{msguniq} option} 165@opindex --sort-by-file@r{, @code{msguniq} option} 166Sort output by file location. 167 168@end table 169 170@subsection Informative output 171 172@table @samp 173@item -h 174@itemx --help 175@opindex -h@r{, @code{msguniq} option} 176@opindex --help@r{, @code{msguniq} option} 177Display this help and exit. 178 179@item -V 180@itemx --version 181@opindex -V@r{, @code{msguniq} option} 182@opindex --version@r{, @code{msguniq} option} 183Output version information and exit. 184 185@end table 186