Hello Osamu,
after a long delay, I am back on po4a. I just commited something to po4a(7) to
make it more explicit that po4a-gettextize should only be used when converting
an existing project to po4a, and that po4a-update should be used (or even
better: po4a) instead on a regular basis. I would
Martin,
On Tue, 2022-09-27 at 09:38 +0200, Martin Quinson wrote:
> 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
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
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 sloow
answer.
I think that the deprecation is not involved in your problem. It's another
issue. I recently realized that some people were
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
5 matches
Mail list logo
