1MSGMERGE(1)                      User Commands                     MSGMERGE(1)
2
3
4

NAME

6       msgmerge - merge message catalog and template
7

SYNOPSIS

9       msgmerge [OPTION] def.po ref.pot
10

DESCRIPTION

12       Merges  two  Uniforum  style .po files together.  The def.po file is an
13       existing PO file with translations which will  be  taken  over  to  the
14       newly  created  file as long as they still match; comments will be pre‐
15       served, but extracted comments and file positions  will  be  discarded.
16       The  ref.pot  file  is  the last created PO file with up-to-date source
17       references but old translations, or a PO Template file (generally  cre‐
18       ated  by  xgettext);  any  translations or comments in the file will be
19       discarded, however dot comments and file positions will  be  preserved.
20       Where an exact match cannot be found, fuzzy matching is used to produce
21       better results.
22
23       Mandatory arguments to long options are  mandatory  for  short  options
24       too.
25
26   Input file location:
27       def.po translations referring to old sources
28
29       ref.pot
30              references to new sources
31
32       -D, --directory=DIRECTORY
33              add DIRECTORY to list for input files search
34
35       -C, --compendium=FILE
36              additional  library  of  message  translations, may be specified
37              more than once
38
39   Operation mode:
40       -U, --update
41              update def.po, do nothing if def.po already up to date
42
43   Output file location:
44       -o, --output-file=FILE
45              write output to specified file
46
47       The results are written to standard output if no output file is  speci‐
48       fied or if it is -.
49
50       Output  file  location  in  update  mode: The result is written back to
51       def.po.
52
53       --backup=CONTROL
54              make a backup of def.po
55
56       --suffix=SUFFIX
57              override the usual backup suffix
58
59       The version control method may be selected via the --backup  option  or
60       through the VERSION_CONTROL environment variable.  Here are the values:
61
62       none, off
63              never make backups (even if --backup is given)
64
65       numbered, t
66              make numbered backups
67
68       existing, nil
69              numbered if numbered backups exist, simple otherwise
70
71       simple, never
72              always make simple backups
73
74       The  backup  suffix  is  '~',  unless  set  with  --suffix  or the SIM‐
75       PLE_BACKUP_SUFFIX environment variable.
76
77   Operation modifiers:
78       -m, --multi-domain
79              apply ref.pot to each of the domains in def.po
80
81       --for-msgfmt
82              produce output for 'msgfmt', not for a translator
83
84       -N, --no-fuzzy-matching
85              do not use fuzzy matching
86
87       --previous
88              keep previous msgids of translated messages
89
90   Input file syntax:
91       -P, --properties-input
92              input files are in Java .properties syntax
93
94       --stringtable-input
95              input files are in NeXTstep/GNUstep .strings syntax
96
97   Output details:
98       --lang=CATALOGNAME
99              set 'Language' field in the header entry
100
101       --color
102              use colors and other text attributes always
103
104       --color=WHEN
105              use colors and other text  attributes  if  WHEN.   WHEN  may  be
106              'always', 'never', 'auto', or 'html'.
107
108       --style=STYLEFILE
109              specify CSS style rule file for --color
110
111       -e, --no-escape
112              do not use C escapes in output (default)
113
114       -E, --escape
115              use C escapes in output, no extended chars
116
117       --force-po
118              write PO file even if empty
119
120       -i, --indent
121              indented output style
122
123       --no-location
124              suppress '#: filename:line' lines
125
126       -n, --add-location
127              preserve '#: filename:line' lines (default)
128
129       --strict
130              strict Uniforum output style
131
132       -p, --properties-output
133              write out a Java .properties file
134
135       --stringtable-output
136              write out a NeXTstep/GNUstep .strings file
137
138       -w, --width=NUMBER
139              set output page width
140
141       --no-wrap
142              do  not  break  long  message lines, longer than the output page
143              width, into several lines
144
145       -s, --sort-output
146              generate sorted output
147
148       -F, --sort-by-file
149              sort output by file location
150
151   Informative output:
152       -h, --help
153              display this help and exit
154
155       -V, --version
156              output version information and exit
157
158       -v, --verbose
159              increase verbosity level
160
161       -q, --quiet, --silent
162              suppress progress indicators
163

AUTHOR

165       Written by Peter Miller.
166

REPORTING BUGS

168       Report    bugs    in    the    bug    tracker    at     <https://savan‐
169       nah.gnu.org/projects/gettext> or by email to <bug-gettext@gnu.org>.
170

COPYRIGHT

172       Copyright  ©  1995-2019 Free Software Foundation, Inc.  License GPLv3+:
173       GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
174       This is free software: you are free  to  change  and  redistribute  it.
175       There is NO WARRANTY, to the extent permitted by law.
176

SEE ALSO

178       The  full documentation for msgmerge is maintained as a Texinfo manual.
179       If the info and msgmerge programs are properly installed at your  site,
180       the command
181
182              info msgmerge
183
184       should give you access to the complete manual.
185
186
187
188GNU gettext-tools 20190512         May 2019                        MSGMERGE(1)