2 @cindex @code{msgcomm} program, usage
4 msgcomm [@var{option}] [@var{inputfile}]...
7 @cindex find common messages
8 The @code{msgcomm} program finds messages which are common to two or more
9 of the specified PO files.
10 By using the @code{--more-than} option, greater commonality may be requested
11 before messages are printed. Conversely, the @code{--less-than} option may be
12 used to specify less commonality before messages are printed (i.e.@:
13 @samp{--less-than=2} will only print the unique messages). Translations,
14 comments and extracted comments will be preserved, but only from the first
15 PO file to define them. File positions from all PO files will be
18 @subsection Input file location
21 @item @var{inputfile} @dots{}
25 @itemx --files-from=@var{file}
26 @opindex -f@r{, @code{msgcomm} option}
27 @opindex --files-from@r{, @code{msgcomm} option}
28 Read the names of the input files from @var{file} instead of getting
29 them from the command line.
31 @item -D @var{directory}
32 @itemx --directory=@var{directory}
33 @opindex -D@r{, @code{msgcomm} option}
34 @opindex --directory@r{, @code{msgcomm} option}
35 Add @var{directory} to the list of directories. Source files are
36 searched relative to this list of directories. The resulting @file{.po}
37 file will be written relative to the current directory, though.
41 If @var{inputfile} is @samp{-}, standard input is read.
43 @subsection Output file location
47 @itemx --output-file=@var{file}
48 @opindex -o@r{, @code{msgcomm} option}
49 @opindex --output-file@r{, @code{msgcomm} option}
50 Write output to specified file.
54 The results are written to standard output if no output file is specified
57 @subsection Message selection
61 @itemx --less-than=@var{number}
62 @opindex -<@r{, @code{msgcomm} option}
63 @opindex --less-than@r{, @code{msgcomm} option}
64 Print messages with less than @var{number} definitions, defaults to infinite
68 @itemx --more-than=@var{number}
69 @opindex ->@r{, @code{msgcomm} option}
70 @opindex --more-than@r{, @code{msgcomm} option}
71 Print messages with more than @var{number} definitions, defaults to 1 if not
76 @opindex -u@r{, @code{msgcomm} option}
77 @opindex --unique@r{, @code{msgcomm} option}
78 Shorthand for @samp{--less-than=2}. Requests that only unique messages be
83 @subsection Input file syntax
87 @itemx --properties-input
88 @opindex -P@r{, @code{msgcomm} option}
89 @opindex --properties-input@r{, @code{msgcomm} option}
90 Assume the input files are Java ResourceBundles in Java @code{.properties}
91 syntax, not in PO file syntax.
93 @item --stringtable-input
94 @opindex --stringtable-input@r{, @code{msgcomm} option}
95 Assume the input files are NeXTstep/GNUstep localized resource files in
96 @code{.strings} syntax, not in PO file syntax.
100 @subsection Output details
102 @c --no-escape and --escape omitted on purpose. They are not useful.
106 @itemx --color=@var{when}
107 @opindex --color@r{, @code{msgcomm} option}
108 Specify whether or when to use colors and other text attributes.
109 See @ref{The --color option} for details.
111 @item --style=@var{style_file}
112 @opindex --style@r{, @code{msgcomm} option}
113 Specify the CSS style rule file to use for @code{--color}.
114 See @ref{The --style option} for details.
117 @opindex --force-po@r{, @code{msgcomm} option}
118 Always write an output file even if it contains no message.
122 @opindex -i@r{, @code{msgcomm} option}
123 @opindex --indent@r{, @code{msgcomm} option}
124 Write the .po file using indented style.
127 @opindex --no-location@r{, @code{msgcomm} option}
128 Do not write @samp{#: @var{filename}:@var{line}} lines.
131 @itemx --add-location
132 @opindex -n@r{, @code{msgcomm} option}
133 @opindex --add-location@r{, @code{msgcomm} option}
134 Generate @samp{#: @var{filename}:@var{line}} lines (default).
137 @opindex --strict@r{, @code{msgcomm} option}
138 Write out a strict Uniforum conforming PO file. Note that this
139 Uniforum format should be avoided because it doesn't support the
143 @itemx --properties-output
144 @opindex -p@r{, @code{msgcomm} option}
145 @opindex --properties-output@r{, @code{msgcomm} option}
146 Write out a Java ResourceBundle in Java @code{.properties} syntax. Note
147 that this file format doesn't support plural forms and silently drops
150 @item --stringtable-output
151 @opindex --stringtable-output@r{, @code{msgcomm} option}
152 Write out a NeXTstep/GNUstep localized resource file in @code{.strings} syntax.
153 Note that this file format doesn't support plural forms.
155 @item -w @var{number}
156 @itemx --width=@var{number}
157 @opindex -w@r{, @code{msgcomm} option}
158 @opindex --width@r{, @code{msgcomm} option}
159 Set the output page width. Long strings in the output files will be
160 split across multiple lines in order to ensure that each line's width
161 (= number of screen columns) is less or equal to the given @var{number}.
164 @opindex --no-wrap@r{, @code{msgcomm} option}
165 Do not break long message lines. Message lines whose width exceeds the
166 output page width will not be split into several lines. Only file reference
167 lines which are wider than the output page width will be split.
171 @opindex -s@r{, @code{msgcomm} option}
172 @opindex --sort-output@r{, @code{msgcomm} option}
173 Generate sorted output. Note that using this option makes it much harder
174 for the translator to understand each message's context.
177 @itemx --sort-by-file
178 @opindex -F@r{, @code{msgcomm} option}
179 @opindex --sort-by-file@r{, @code{msgcomm} option}
180 Sort output by file location.
183 @opindex --omit-header@r{, @code{msgcomm} option}
184 Don't write header with @samp{msgid ""} entry.
188 @subsection Informative output
193 @opindex -h@r{, @code{msgcomm} option}
194 @opindex --help@r{, @code{msgcomm} option}
195 Display this help and exit.
199 @opindex -V@r{, @code{msgcomm} option}
200 @opindex --version@r{, @code{msgcomm} option}
201 Output version information and exit.