Hi, You are correct. I was using po4a-gettextize to update PO.
Good news is migration to pure po4a command only approach is not much of work. Just a bit more CPU time waisted but ... it is actually cleaner. After initial surprise, I tried a few experimental builds with cool head. I realized I can easily migrate to pure po4a-way even for a document with lots (2.5K msgid) of auto-generated contents without burdening the translators. Excluding 2.5K msgids is important for each translators. Just for the record, let me write down this for the record. * create original English document * create filtered and trimmed English document * move existing po's to po4a places (Maybe this can be avoided but I wanted simple proven set up) * po4a -v po4a/po4a.cfg * use po4a/po4a.cfg to create and update PO using po4a in po4a/po * Useless generation of filtered translated document is the side effect * cp -r po4a po4a-tmp * cp -f po4a-tmp.cfg po4a-tmp/po4a-tmp.cfg * po4a -v po4a-tmp/po4a-tmp.cfg * use po4a-tmp/po4a-tmp.cfg to create and update PO using po4a (no need to store result) * Important generation of full translated document * rm -rf po4a-tmp Pure po4a approach doesn't allow me to use auto translation between zh-tw and zh-cn but this is not so critical. Maybe this can be addressed too with the help of gettext package and script. (Instead of just "cp -r", we run script I suppose.) On Tue, 2022-09-27 at 09:38 +0200, Martin Quinson wrote: > Hello, > > Here is a quick first answer. I'll check more later but I'm busy these days > so I > have to do a fast approximate answer, or you'll have to wait for a sloooooow > answer. > > I think that the deprecation is not involved in your problem. It's another > issue. I recently realized that some people were using po4a-gettextize in > place > of po4a-updatepo to create the po, even if that's absolutely not the expected > way of using tools. That use of po4a-gettextize is not expected by the code, > so > thing may well go wrong, either now or in the future. This is why I decided to > drop that use of po4a-gettextize. > > Please try to use po4a-updatepo instead and tell me if it solves the issue as > I > suspect. > > Thanks for your time and for reporting, > Mt > > Le mardi 27 septembre 2022 à 15:40 +0900, Osamu Aoki a écrit : > > Package: po4a > > Version: 0.68-1 > > Severity: normal > > > > Hi, > > > > I am experiencing FTBFS on debian-reference and maint-guide > > > > If you want to deprecate po4a-translate and po4a-updatepo and force me > > to use po4a, that's sad but I understand your position. Maintenance of > > them may be burden for you. But can we do this with a bit more > > coordination and with transition period. > > > > I am facing problem with new 0.68-1 > > > > - Greatly improve the gettextization process > > - po4a-translate and po4a-updatepo are now deprecated: > > you should use po4a instead. > > > > Error I am facing is as follows: > > ---- > > po4a-gettextize -M utf-8 -L utf-8 --format docbook -m > > debian-reference.en.xmlt > > > \ > > sed -e 's,^"Content-Type: text/plain; charset=CHARSET\\n"$,"Content-Type: > > text/plain; charset=UTF-8\\n",' |\ > > msgcat --no-location -o po/templates.pot.new - > > You must provide the same amount of master files and localized files to > > synchronize them, as po4a-gettextize is intended to synchronize master files > > and previously existing translations. If just want to extract POT files of > > your master files, please use po4a-updatepo. Please note that the most > > convenient way of using po4a is to write a po4a.conf file and use the > > integrated po4a(1) program. > > if diff -I '^"POT-Creation-Date:' -q po/templates.pot po/templates.pot.new ; > > then \ > > echo "Don't update templates.pot" ;\ > > touch po/templates.pot ;\ > > rm -f po/templates.pot.new ;\ > > else \ > > echo "Update templates.pot" ;\ > > mv -f po/templates.pot.new po/templates.pot ;\ > > fi > > diff: po/templates.pot: No such file or directory > > diff: po/templates.pot.new: No such file or directory > > ---- > > > > template.pot is not generated by po4a-gettext any more > > > > I intensionally touch-up master file to reduce translation PO file size > > by placing "DUMMY" to certain master file contents used by > > po4a-gettextize. So those parts doesn't apear in po/pot and translator > > have easier time. In order to attain this, I directly use > > po4a-translate and po4a-updatepo from Makefile to get translated results > > with the full English file with reduced size PO. > > > > Please also realize that my Makefile also use opencc to translate > > missing translation msgstr in PO files supplimenting between zh_CN and > > zh_TW peacefully. po4a command has no way to do this either. > > > > Since this failure seems to be induced by the newly added sanity check > > to force us to migrate to use po4a, I am asking you to go slow on this > > migration. Can you just give us option to avoid this failure at least > > for the next release? Do you really force this sanity check now? > > > > I hope to come up with new build script using po4a. But unless that > > happens, debian-reference and maint-guide will be out of testing. > > > > > > > > -- System Information: > > Debian Release: bookworm/sid > > APT prefers testing > > APT policy: (500, 'testing') > > Architecture: amd64 (x86_64) > > > > Kernel: Linux 5.19.0-1-amd64 (SMP w/12 CPU threads; PREEMPT) > > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > > LANGUAGE=en_US:en > > Shell: /bin/sh linked to /usr/bin/dash > > Init: systemd (via /run/systemd/system) > > LSM: AppArmor: enabled > > > > Versions of packages po4a depends on: > > ii gettext 0.21-9 > > 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-2 > > ii libtext-wrapi18n-perl 0.06-10 > > ii libunicode-linebreak-perl 0.0.20190101-1+b4 > > > > po4a suggests no packages. > > > > -- no debconf information >
