Hello, the short answer is that po4a-gettextize is not intended to be used on a regular basis. It's only intended for the first run when you want to convert an existing translation to the po-based workflow. Once it's done, you're supposed to use po4a-updatepo to create an empty PO file. Even better, you should use po4a directly instead of the deprecated atomic commands.
The extra spaces that you see are intended to help the gettextization process, as explained in the po4a-gettextize manpage. I'm not sure of how I can help you here. What piece of documentation should be updated? Thanks for using po4a, Mt Le vendredi 05 août 2022 à 16:02 +0200, Helge Kreutzmann a écrit : > Package: po4a > Version: 0.67-2 > Severity: normal > Tags: upstream > X-Debbugs-Cc: Ben Hutchings <b...@decadent.org.uk> > > > I'm the translator of the German translation for the documentation of > sgt-puzzles. It is a Debian-only patch at the moment for the halibut > based sources. > > A few days ago Ben (the Debian maintainer) updated the package and > requested me to update the German translation. While doing so he > noticed a strange change in po4a behaviour: > > (Some) strings, which are repeated (because the same text appears in > multiple places in the documentation resp. many man pages) are > inserted several times into de.po, except that an increasing number of > spaces is added, i.e. > > "dog" would become > "dog" > "dog " > "dog " > "dog " > and so on. > > While updating the German translation of po4a I remember translating > something along these lines, though I did not fully understand its > meaning. > > This behaviour defeats part of the idea of the po format. Unless the > orginal author indicates this, identical strings in the original text > should be translated identical as well. > > Now for some reason po4a makes identical strings artificially different. > > In the toy example above, this could become: > "Hund" > "Rüde " > "Gerüstklammer " > "Schlepphaken " > … > > So now the same string is translated differently *and* the > translation receives also (varying) additional trailing spaces. (As a > translator, you usually reproduce space at the beginning and end). > > In this toy example this might be noticed easily, but usually po4a is > used for (longer) paragraphs - and translators might not realize they > already translated them and would retranslate them - additional work > and, as stated above, potentially inconsistent translations. > > Thus please revert to the previous behaviour of po4a *or* ensure that > identical text is shown only once in the *.po(t) files. > > In case you want to investigate yourself, do the following in > unstable: > > apt-get source sgt-puzzles > cd sgt-puzzles-20191231.79a5378/ > make -f debian/rules build > make -f Makefile.doc update-po > > > -- System Information: > Debian Release: bookworm/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.18.15 (SMP w/12 CPU threads) > Kernel taint flags: TAINT_UNSIGNED_MODULE > 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-6 > ii libpod-parser-perl 1.65-1 > ii libsgmls-perl 1.03ii-37 > ii libsyntax-keyword-try-perl 0.27-1 > ii libyaml-tiny-perl 1.73-1 > ii opensp 1.5.2-13+b2 > ii perl 5.34.0-5 > > Versions of packages po4a recommends: > ii liblocale-gettext-perl 1.07-4+b2 > ii libterm-readkey-perl 2.38-1+b3 > ii libtext-wrapi18n-perl 0.06-9 > ii libunicode-linebreak-perl 0.0.20190101-1+b4 > > po4a suggests no packages. > > -- no debconf information > -- Pour une évaluation indépendante, transparente et rigoureuse ! Je soutiens la Commission d'Évaluation de l'Inria.
signature.asc
Description: This is a digitally signed message part
