Hello Martin, On Mon, Jun 05, 2023 at 11:32:04PM +0200, Martin Quinson wrote: > Every po4a-* scripts are deprecated. The right way to go is to use the main > po4a script, using an adequate config file. I think that this is documented in > po4a(1), isn't it?
Yes, po4a is documented, but not the work flow we use. The
documentation assumes an intial "run" with a previous translation and
then po4a. (See my report you cite below).
> Which project are we speaking of? I'm really overwhelmed right now but maybe I
> could find some time to propose a config file for that project in the future.
This is not only a config file. We have several scripts which prepare
the pot files, manage the compendium, deal with upstream files etc. So
this is a large machinery.
The project is manpages-l10n. We have 2319 pot files, 22 languages, 8
distributions we take files from, over 100 projects the man pages come
from 9597 po files, organized nicely by languages, man page section.
All scripts are written to allow easy additions of new languages (and
indeed, we get more and more of them).
My intent is to understand the proper way to do things and then to see
if I'm able to migrate our scripts doing just this. This, of course,
is a long term project.
> Sorry,
No need to be, we are all volunteers; thanks for your work on po4a!
> Mt
>
> Le samedi 27 mai 2023 à 13:56 +0200, Helge Kreutzmann a écrit :
> > Package: po4a
> > Version: 0.69-1
> > Severity: wishlist
> >
> > Some time ago 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/request:
> > 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)
> >
> > It would be great if you could document the proper solution in the
> > very well written and extensive documentation.
> >
> >
> > -- System Information:
> > Debian Release: 12.0
> > APT prefers testing-security
> > APT policy: (500, 'testing-security'), (500, 'testing')
> > Architecture: amd64 (x86_64)
> >
> > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored:
> > LC_ALL set to de_DE.UTF-8), LANGUAGE not set
> > Shell: /bin/sh linked to /usr/bin/dash
> > Init: systemd (via /run/systemd/system)
> >
> > Versions of packages po4a depends on:
> > ii gettext 0.21-12
> > ii libpod-parser-perl 1.65-1
> > ii libsgmls-perl 1.03ii-38
> > ii libsyntax-keyword-try-perl 0.28-1
> > ii libyaml-tiny-perl 1.73-1
> > ii opensp 1.5.2-13+b2
> > ii perl 5.36.0-7
> >
> > Versions of packages po4a recommends:
> > ii liblocale-gettext-perl 1.07-5
> > ii libterm-readkey-perl 2.38-2+b1
> > ii libtext-wrapi18n-perl 0.06-10
> > ii libunicode-linebreak-perl 0.0.20190101-1+b5
> >
> > po4a suggests no packages.
> >
> > -- no debconf information
Greetings
Helge
--
Dr. Helge Kreutzmann [email protected]
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: PGP signature
