|
|
36.
|
|
|
So, the whole point of po4a is to make the documentation translation I<maintainable>. The idea is to reuse the gettext methodology to this new field. Like in gettext, texts are extracted from their original locations in order to be presented in a uniform format to the translators. The classical gettext tools help them updating their works when a new release of the original comes out. But to the difference of the classical gettext model, the translations are then re-injected in the structure of the original document so that they can be processed and distributed just like the English version.
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:123
|
|
|
37.
|
|
|
Thanks to this, discovering which parts of the document were changed and need an update becomes very easy. Another good point is that the tools will make almost all the work when the structure of the original document gets fundamentally reorganized and when some chapters are moved around, merged or split. By extracting the text to translate from the document structure, it also keeps you away from the text formatting complexity and reduces your chances to get a broken document (even if it does not completely prevent you to do so).
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:133
|
|
|
38.
|
|
|
Please also see the L<FAQ> below in this document for a more complete list of the advantages and disadvantages of this approach.
|
|
|
type: textblock
|
|
|
|
|
Por favor, veja também o L<FAQ> a seguir no presente documento para uma lista mais completa das vantagens e desvantagens desta abordagem.
|
|
Translated and reviewed by
durammx
|
|
|
|
Located in
doc/po4a.7.pod:141
|
|
|
39.
|
|
|
Supported formats
|
|
|
type: =head2
|
|
|
|
|
Formatos suportados
|
|
Translated and reviewed by
xx
|
|
|
|
Located in
share/doc//po4a-build.xml:79 doc/po4a-build.conf.5.pod:30 doc/po4a.7.pod:144
|
|
|
40.
|
|
|
Currently, this approach has been successfully implemented to several kinds of text formatting formats:
|
|
|
type: textblock
|
|
|
|
|
Actualmente, esta abordagem tem sido aplicada com sucesso a vários tipos de formatos de formatação de texto:
|
|
Translated and reviewed by
xx
|
|
|
|
Located in
doc/po4a.7.pod:146
|
|
|
41.
|
|
|
nroff
|
|
|
type: =head3
|
|
|
|
|
nroff
|
|
Translated and reviewed by
xx
|
|
|
|
Located in
doc/po4a.7.pod:149
|
|
|
42.
|
|
|
The good old manual pages' format, used by so much programs out there. The po4a support is very welcome here since this format is somewhat difficult to use and not really friendly to the newbies. The L<Locale::Po4a::Man(3pm)|Man> module also supports the mdoc format, used by the BSD man pages (they are also quite common on Linux).
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:151
|
|
|
43.
|
|
|
pod
|
|
|
type: =head3
|
|
|
|
|
pod
|
|
Translated and reviewed by
durammx
|
|
|
|
Located in
doc/po4a.7.pod:157
|
|
|
44.
|
|
|
This is the Perl Online Documentation format. The language and extensions themselves are documented that way, as well as most of the existing Perl scripts. It makes easy to keep the documentation close to the actual code by embedding them both in the same file. It makes programmer life easier, but unfortunately, not the translator one.
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:159
|
|
|
45.
|
|
|
sgml
|
|
|
type: =head3
|
|
|
|
|
sgml
|
|
Translated and reviewed by
xx
|
|
|
|
Located in
doc/po4a.7.pod:165
|
