Experience with perl pod handling?
by Helge Kreutzmann
Hello po4a maintainers,
we recently had a first translation of a perl man page in
manpages-l10n. In your documentation (in the man pages) I read that
you have lots of experience handling perl documentations, so I hope
you can help me.
The perl(1) man page introduces the macro
.de Vb \" Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \" End verbatim text
and then perl.1 uses this to create tables, e.g.:
Overview
perl Perl overview (this section)
perlintro Perl introduction for beginners
perlrun Perl execution and options
perltoc Perl documentation table of contents
This table becomes
#. type: IX
#: debian-bullseye debian-unstable fedora-37 fedora-rawhide mageia-cauldron
#: opensuse-leap-15-5 opensuse-tumbleweed
#, no-wrap
msgid "Overview"
msgstr "Überblick"
#. type: IX
#: debian-bullseye debian-unstable fedora-37 fedora-rawhide mageia-cauldron
#: opensuse-leap-15-5 opensuse-tumbleweed
#, no-wrap
msgid "Subsection"
msgstr "Subsection"
#. type: Plain text
#: debian-bullseye debian-unstable fedora-37 fedora-rawhide mageia-cauldron
#: opensuse-leap-15-5 opensuse-tumbleweed
msgid ""
"\\& perl Perl overview (this section) \\& perlintro Perl introduction for "
"beginners \\& perlrun Perl execution and options \\& perltoc Perl "
"documentation table of contents"
msgstr ""
"\\& perl Perl-Überblick (dieser Abschnitt) \\& perlintro Perl-Einführung "
"für Anfänger \\& perlrun Perl-Ausführung und -Optionen \\& perltoc "
"Inhaltsverzeichnis der Perl-Dokumentation"
in the po file and then the resulting file looks like this:
Überblick
perl Perl-Überblick (dieser Abschnitt) perlintro Perl-Einführung für
Anfänger perlrun Perl-Ausführung und -Optionen perltoc
Inhaltsverzeichnis der Perl-Dokumentation
So the formatting is broken, unfortunately some tables are much longer
in perl.1 …
Do you have any suggestions how to handle this, to unbreak the
situation? I'm running out of ideas.
Thanks!
Greetings
Helge
--
Dr. Helge Kreutzmann debian(a)helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
2 years, 2 months
- 2
- 2
Proper creation of pot files from man pages
by Helge Kreutzmann
Hello po4a maintainers,
I'm Helge and I'm helping Mario to maintain the translation machinery
of manpages-l10n.
Recently several po4a tools started emitting warnings and ceased
working as before. I read that "po4a" is the way to go, however, we
seriously lack the man power (and knowledge) to rewrite the entire
machinery. However, I'm gradully trying to improve the system where
and when possible.
For this, I have the follwing question:
Given that I have a man page (in nroff or mdoc format) and I want to
create a pot file from it (not po file, as this page is not yet
translated). How is this done best/correctly?
Quite a few explanations in the po4a man pages assume you already have
some translated text.
Currently I use something like:
po4a-updatepo -f man \
--option groff_code=verbatim \
--option generated \
--option untranslated="a.RE,\|" \
--option unknown_macros=untranslated \
--master "$upstream_manpage" -M utf-8 \
-p $tmp1 | grep -v "po4a-updatepo is deprecated. The unified po4a(1) program is more convenient and less error prone."
(Until very recently this used po4a-gettextize, but this stopped working)
Thanks for any hints / pointers.
Greetings
Helge
--
Dr. Helge Kreutzmann debian(a)helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
2 years, 2 months
- 1
- 0
- ← Newer
- 1
- Older →