|
|
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
|
|
|
83.
|
|
|
Often, you used to translate manually the document happily until a major reorganization of the original document happened. Then, after some unpleasant tries with diff or similar tools, you want to convert to po4a. But of course, you don't want to loose your existing translation in the process. Don't worry, this case is also handled by po4a tools and is called gettextization.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:371
|
|
|
84.
|
|
|
The key here is to have the same structure in the translated document and in the original one so that the tools can match the content accordingly.
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:384
|
|
|
85.
|
|
|
If you are lucky (i.e., if the structures of both documents perfectly match), it will work seamlessly and you will be set in a few seconds. Otherwise, you may understand why this process has such an ugly name, and you'd better be prepared to some grunt work here. In any case, remember that it is the price to pay to get the comfort of po4a afterward. And the good point is that you have to do so only once.
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:387
|
|
|
86.
|
|
|
I cannot emphasis this too much. In order to ease the process, it is thus important that you find the exact version which were used to do the translation. The best situation is when you noted down the cvs revision used for the translation and you didn't modify it in the translation process, so that you can use it.
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:394
|
|
|
87.
|
|
|
It won't work well when you use the updated original text with the old translation. It remains possible, but is harder and really should be avoided if possible. In fact, I guess that if you fail to find the original text again, the best solution is to find someone to do the gettextization for you (but, please, not me ;).
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:400
|
