1MSGCOMM(1) GNU 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 extract comments will be preserved, but only
18 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 -e, --no-escape
65 do not use C escapes in output (default)
66
67 -E, --escape
68 use C escapes in output, no extended chars
69
70 --force-po
71 write PO file even if empty
72
73 -i, --indent
74 write the .po file using indented style
75
76 --no-location
77 do not write '#: filename:line' lines
78
79 -n, --add-location
80 generate '#: filename:line' lines (default)
81
82 --strict
83 write out strict Uniforum conforming .po file
84
85 -p, --properties-output
86 write out a Java .properties file
87
88 --stringtable-output
89 write out a NeXTstep/GNUstep .strings file
90
91 -w, --width=NUMBER
92 set output page width
93
94 --no-wrap
95 do not break long message lines, longer than the output page
96 width, into several lines
97
98 -s, --sort-output
99 generate sorted output
100
101 -F, --sort-by-file
102 sort output by file location
103
104 --omit-header
105 don't write header with `msgid ""' entry
106
107 Informative output:
108 -h, --help
109 display this help and exit
110
111 -V, --version
112 output version information and exit
113
115 Written by Peter Miller.
116
118 Report bugs to <bug-gnu-gettext@gnu.org>.
119
121 Copyright © 1995-1998, 2000-2006 Free Software Foundation, Inc.
122 This is free software; see the source for copying conditions. There is
123 NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
124 PURPOSE.
125
127 The full documentation for msgcomm is maintained as a Texinfo manual.
128 If the info and msgcomm programs are properly installed at your site,
129 the command
130
131 info msgcomm
132
133 should give you access to the complete manual.
134
135
136
137GNU gettext-tools 0.16.1 November 2006 MSGCOMM(1)