1pomigrate2(1)               Translate Toolkit 1.3.0              pomigrate2(1)
2
3
4

NAME

6       pomigrate2 - Migrates PO files from an old version using new POT files.
7

SYNOPSIS

9       pomigrate [options] from to new-templates
10
11       Where  from  is  a  directory of existing PO files, to is the directory
12       where the migrated PO files will be stored, and  new-templates  is  the
13       directory that contains the PO Template files.
14

DESCRIPTION

16       pomigrate2  aims to move an existing translation to a new version based
17       on updated PO Template files automatically without  user  intervention.
18       Therefore  it  is  ideal  for  when you are migrating many languages or
19       migrating from related but divergent products eg Mozilla to Firefox.
20

OPTIONS

22       -F, --use-fuzzy-matching
23              use fuzzy algorithms when merging to attempt to match strings
24
25       -C, --use-compendium
26              create and use a compendium built from the migrating files
27
28       -C, --use-compendium=some-compendium.po
29              use an external compendium during the migration
30
31       --no-wrap
32              do not wrap long lines
33
34       --locale
35              set locale for newly born files
36
37       -q, --quiet
38              suppress most output
39
40       -p, --pot2po
41              use pot2po(1) instead of msgmerge(1) to migrate (you cannot  use
42              compendia)
43

OPERATION

45       pomigrate2  makes  use of the Gettext tools msgmerge or Translate Tool‐
46       kits pot2po to perform its merging tasks.
47
48       It firstly finds all files with the same name and location in the  from
49       directory  as  in the new-template directory and copies these to the to
50       directory. If there is no file in  the  from  directory  to  match  one
51       needed  by  the new-template directory then it will msgcat(1) all files
52       in the from directory with the same name and copy them to  the  correct
53       destination  in  the to directory. If all of that fails then msginit(1)
54       is used to initialise any missing PO files.
55
56       Lastly all the files in <to> are merged using msgmerge(1) or pot2po(1).
57       This process updates the files to match the layout and messages in new-
58       templates. Optionally, by using --use-compendium, a compendium  of  all
59       the  translations  in from can be created to be used in the final merge
60       process.
61

BUGS

63       None known
64
65
66
67                            Translate Toolkit 1.3.0              pomigrate2(1)
Impressum