|
|
66.
|
|
|
To begin a new translation using po4a, you have to do the following steps:
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:301
|
|
|
67.
|
|
|
-
|
|
|
type: =item
|
|
|
|
|
-
|
|
Translated and reviewed by
Angel Spy
|
|
|
|
Located in
doc/po4a.7.pod:305 doc/po4a.7.pod:318 doc/po4a.7.pod:447 doc/po4a.7.pod:454 doc/po4a.7.pod:462 doc/po4a.7.pod:468 doc/po4a.7.pod:476 doc/po4a.7.pod:489 doc/po4a.7.pod:497 lib/Locale/Po4a/TransTractor.pm:52 lib/Locale/Po4a/TransTractor.pm:56 lib/Locale/Po4a/TransTractor.pm:66 lib/Locale/Po4a/TransTractor.pm:71 lib/Locale/Po4a/TransTractor.pm:764 lib/Locale/Po4a/TransTractor.pm:768 lib/Locale/Po4a/TransTractor.pm:772 lib/Locale/Po4a/TransTractor.pm:808 lib/Locale/Po4a/TransTractor.pm:812 lib/Locale/Po4a/TransTractor.pm:817 lib/Locale/Po4a/TransTractor.pm:1092 lib/Locale/Po4a/TransTractor.pm:1096 lib/Locale/Po4a/TransTractor.pm:1100
|
|
|
68.
|
|
|
Extract the text which have to be translated from the original document into a new pot file (the gettext format). For that, use the I<po4a-gettextize> program that way:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:301
|
|
|
69.
|
|
|
$ po4a-gettextize -f <format> -m <master.doc> -p <translation.pot> 
|
|
|
type: verbatim
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
$ po4a-gettextize -f <format> -m <master.doc> -p <translation.pot>
|
|
Translated and reviewed by
Angel Spy
|
|
|
|
Located in
doc/po4a.7.pod:311
|
|
|
70.
|
|
|
E<lt>formatE<gt> is naturally the format used in the E<lt>master.docE<gt> document. As expected, the output goes into E<lt>translation.potE<gt>. Please refer to L<po4a-gettextize(1)> for more details about the existing options.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:307
|
|
|
71.
|
|
|
Actually translate what should be translated. For that, you have to rename the pot file for example to doc.XX.po (where XX is the ISO639 code of the language you are translating to, e.g. "fr" for French), and edit the resulting file. It is often a good idea to not name the file XX.po to avoid confusion with the translation of the program messages, but this your call. Don't forget to update the po file headers, they are important.
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:320
|
|
|
72.
|
|
|
The actual translation can be done using the Emacs po mode or kbabel (KDE based) or gtranslator (GNOME based), or whichever program you prefer to use them. A good ol' vi could do the trick too, even if there is no specialized mode for this task.
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:327
|
|
|
73.
|
|
|
If you wish to learn more about this, you definitively need to refer to the gettext documentation, available in the B<gettext-doc> package.
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:332
|
|
|
74.
|
|
|
Once you're done with the translation, you want to get the translated documentation and distribute it to users along with the original one. For that, use the L<po4a-translate(1)> program like that (where XX is the language code):
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:339
|
|
|
75.
|
|
|
$ po4a-translate -f <format> -m <master.doc> -p <doc.XX.po> -l <XX.doc>
|
|
|
type: verbatim
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
$ po4a-translate -f <format> -m <master.doc> -p <doc.XX.po> -l <XX.doc>
|
|
Translated and reviewed by
Angel Spy
|
|
|
|
Located in
doc/po4a.7.pod:344
|
