1PO4A-GETTEXTIZE(1) User Contributed Perl Documentation PO4A-GETTEXTIZE(1)
2
3
4
6 po4a-gettextize - convert an original file (and its translation) to a
7 po file
8
10 po4a-gettextize -f <fmt> -m <master.doc> [-l <XX.doc>] -p <XX.po>
11
12 (XX.po is the output, all others are inputs)
13
15 The po4a (po for anything) project goal is to ease translations (and
16 more interestingly, the maintenance of translations) using gettext
17 tools on areas where they were not expected like documentation.
18
19 The "po4a-gettextize" script is in charge of converting documentation
20 files to po files. If you start a new translation, "po4a-gettextize"
21 will extract the translatable strings from the documentation file and
22 write a pot file from it.
23
24 If you already have a translated file, "po4a-gettextize" will try to
25 extract the translations it contains and put them in place in the writ‐
26 ten po file. Be warned that very few intelligence is used in this
27 process: the Nth string of the translated file is supposed to be the
28 translation of the Nth string in the original. If it's not the case,
29 you're dead. That's why it is very important that both files share
30 exactly the same structure.
31
32 However, "po4a-gettextize" will diagnose your death by detecting any
33 desynchronisation between files, and reporting where they occur. In
34 that case, you should edit manually the files to solve the reported
35 disparity. Even if no error were reported, you should check carefully
36 that the generated po file is correct (ie, that each msgstr is the
37 translation of the associated msgid, and not the one before or after).
38
39 Even if the script manages to do its job without any apparent problem,
40 it still marks all extracted translations as fuzzy, to make sure that
41 the translator will have a look at them, and detect any remaining prob‐
42 lem.
43
44 If the master document has non-ascii characters, the new generated po
45 file will be in utf-8, in order to allow non-standard characters in a
46 culture independent way. Else (if the master document is completely in
47 ascii), the generated po will use the encoding of the translated input
48 document.
49
51 -f, --format
52 Format of the documentation you want to handle. Use the --help-for‐
53 mat option to see the list of available formats.
54
55 -m, --master
56 File containing the master document to translate. You can use this
57 option multiple times if you want to gettextize multiple documents.
58
59 -M, --master-charset
60 Charset of the file containing the document to translate.
61
62 -l, --localized
63 File containing the localized (translated) document. If you pro‐
64 vided multiple master files, you may wish to provide multiple
65 localized file by using this option more than once.
66
67 -L, --localized-charset
68 Charset of the file containing the localized document.
69
70 -p, --po
71 File where the message catalog should be written. If not given, the
72 message catalog will be written to the standard output.
73
74 -o, --option
75 Extra option(s) to pass to the format plugin. Specify each option
76 in the 'name=value' format. See the documentation of each plugin
77 for more information about the valid options and their meanings.
78
79 -h, --help
80 Show a short help message.
81
82 --help-format
83 List the documentation format understood by po4a.
84
85 -V, --version
86 Display the version of the script and exit.
87
88 -v, --verbose
89 Increase the verbosity of the program.
90
91 -d, --debug
92 Output some debugging information.
93
95 po4a(7), po4a-updatepo(1), po4a-translate(1), po4a-normalize(1).
96
98 Denis Barbier <barbier@linuxfr.org>
99 Martin Quinson (mquinson#debian.org)
100
102 Copyright 2002, 2003, 2004 by SPI, inc.
103
104 This program is free software; you may redistribute it and/or modify it
105 under the terms of GPL (see the COPYING file).
106
107
108
109perl v5.8.8 2008-06-01 PO4A-GETTEXTIZE(1)