|
|
15.
|
|
|
HOWTO add extra text to translations (like translator's name)?
|
|
|
type: =head2
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:40 doc/po4a.7.pod:538
|
|
|
52.
|
|
|
The XML format is a base format for many documentation formats.
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:195
|
|
|
60.
|
|
|
Graphical overview
|
|
|
type: =head2
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:227
|
|
|
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
|
|
|
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
|
|
|
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
|
|
|
115.
|
|
|
Here are the possible header keys:
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:570
|
|
|
130.
|
|
|
In our case, we can choose to indicate the end of the section we match by adding:
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:620
|
|
|
132.
|
|
|
or to indicate the beginning of the next section by indicating:
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:625
|
|
|
136.
|
|
|
This can seem obscure, but hopefully, the next examples will enlighten you.
|
|
|
type: textblock
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
doc/po4a.7.pod:644
|
