|
|
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
|
|
|
76.
|
|
|
As before, E<lt>formatE<gt> is the format used in the E<lt>master.docE<gt> document. But this time, the po file provided with the -p flag is part of the input. This is your translation. The output goes into E<lt>XX.docE<gt>.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:340
|
|
|
77.
|
|
|
Please refer to L<po4a-translate(1)> for more details.
|
|
|
type: textblock
|
|
|
|
|
Lütfen daha fazla detay için L<po4a-translate(1)> e başvurun.
|
|
Translated by
ubuntuki
|
|
Reviewed by
Angel Spy
|
|
|
|
Located in
doc/po4a.7.pod:350
|
|
|
78.
|
|
|
To update your translation when the original file has changed, use the L<po4a-updatepo(1)> program like that:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:348
|
|
|
79.
|
|
|
$ po4a-updatepo -f <format> -m <new_original.doc> -p <existing.XX.po>
|
|
|
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.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:351
|
|
|
80.
|
|
|
(Please refer to L<po4a-updatepo(1)> for more details)
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:359
|
|
|
81.
|
|
|
Naturally, the new paragraph in the document won't get magically translated in the C<po> file with this operation, and you'll need to update the C<po> file manually. Likewise, you may have to rework the translation for paragraphs which were modified a bit. To make sure you won't miss any of them, they are marked as "fuzzy" during the process and you have to remove this marker before the translation can be used by po4a-translate. As for the initial translation, the best is to use your favorite po editor here.
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:361
|
|
|
82.
|
|
|
Once your C<po> file is up-to-date again, without any untranslated or fuzzy string left, you can generate a translated documentation file, as explained in the previous section.
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:370
|
