1MSGCOMM(1) User Commands MSGCOMM(1)
2
3
4
6 msgcomm - match two message catalogs
7
9 msgcomm [OPTION] [INPUTFILE]...
10
12 Find messages which are common to two or more of the specified PO
13 files. By using the --more-than option, greater commonality may be
14 requested before messages are printed. Conversely, the --less-than
15 option may be used to specify less commonality before messages are
16 printed (i.e. --less-than=2 will only print the unique messages).
17 Translations, comments and extracted comments will be preserved, but
18 only from the first PO file to define them. File positions from all PO
19 files will be cumulated.
20
21 Mandatory arguments to long options are mandatory for short options
22 too.
23
24 Input file location:
25 INPUTFILE ...
26 input files
27
28 -f, --files-from=FILE
29 get list of input files from FILE
30
31 -D, --directory=DIRECTORY
32 add DIRECTORY to list for input files search
33
34 If input file is -, standard input is read.
35
36 Output file location:
37 -o, --output-file=FILE
38 write output to specified file
39
40 The results are written to standard output if no output file is speci‐
41 fied or if it is -.
42
43 Message selection:
44 -<, --less-than=NUMBER
45 print messages with less than this many definitions, defaults to
46 infinite if not set
47
48 ->, --more-than=NUMBER
49 print messages with more than this many definitions, defaults to
50 1 if not set
51
52 -u, --unique
53 shorthand for --less-than=2, requests that only unique messages
54 be printed
55
56 Input file syntax:
57 -P, --properties-input
58 input files are in Java .properties syntax
59
60 --stringtable-input
61 input files are in NeXTstep/GNUstep .strings syntax
62
63 Output details:
64 --color
65 use colors and other text attributes always
66
67 --color=WHEN
68 use colors and other text attributes if WHEN. WHEN may be
69 'always', 'never', 'auto', or 'html'.
70
71 --style=STYLEFILE
72 specify CSS style rule file for --color
73
74 -e, --no-escape
75 do not use C escapes in output (default)
76
77 -E, --escape
78 use C escapes in output, no extended chars
79
80 --force-po
81 write PO file even if empty
82
83 -i, --indent
84 write the .po file using indented style
85
86 --no-location
87 do not write '#: filename:line' lines
88
89 -n, --add-location
90 generate '#: filename:line' lines (default)
91
92 --strict
93 write out strict Uniforum conforming .po file
94
95 -p, --properties-output
96 write out a Java .properties file
97
98 --stringtable-output
99 write out a NeXTstep/GNUstep .strings file
100
101 -w, --width=NUMBER
102 set output page width
103
104 --no-wrap
105 do not break long message lines, longer than the output page
106 width, into several lines
107
108 -s, --sort-output
109 generate sorted output
110
111 -F, --sort-by-file
112 sort output by file location
113
114 --omit-header
115 don't write header with 'msgid ""' entry
116
117 Informative output:
118 -h, --help
119 display this help and exit
120
121 -V, --version
122 output version information and exit
123
125 Written by Peter Miller.
126
128 Report bugs in the bug tracker at <https://savan‐
129 nah.gnu.org/projects/gettext> or by email to <bug-gettext@gnu.org>.
130
132 Copyright © 1995-2020 Free Software Foundation, Inc. License GPLv3+:
133 GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
134 This is free software: you are free to change and redistribute it.
135 There is NO WARRANTY, to the extent permitted by law.
136
138 The full documentation for msgcomm is maintained as a Texinfo manual.
139 If the info and msgcomm programs are properly installed at your site,
140 the command
141
142 info msgcomm
143
144 should give you access to the complete manual.
145
146
147
148GNU gettext-tools 20200704 July 2020 MSGCOMM(1)