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 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. I think you need to update po4a(7) page. The use case of po4a-gettext to create POT is written there. I updated this file when I added this overcomplicated use case. Overcomplicated tool situation is tough to maintain. But, if you drop support, please match docs. The thing is I now realize I can get the equivalent just using po4a command only. (Running twice) Use of po4a-updatepo may save me some build time but I am now keeping it simple to use po4a. As for openCC use with po4a, it was rather simple to do. debian-reference will be OK soon. Osamu
