Am 13.01.24 um 20:25 schrieb Helge Kreutzmann:
Hello Martin,
Am Fri, Jan 05, 2024 at 05:32:37PM +0100 schrieb Martin Quinson:
I just revamped the po4a(7) documentation to better explain the workflow using
po4a only, without po4a-translate and po4a-updatepo. The result is unreleased
for now, but
Hello Martin,
Am Fri, Jan 05, 2024 at 05:32:37PM +0100 schrieb Martin Quinson:
> I just revamped the po4a(7) documentation to better explain the workflow using
> po4a only, without po4a-translate and po4a-updatepo. The result is unreleased
> for now, but already viewable here:
>
tag 1036824 fixed-upstream
thanks
Hello Helge,
I just revamped the po4a(7) documentation to better explain the workflow using
po4a only, without po4a-translate and po4a-updatepo. The result is unreleased
for now, but already viewable here:
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
Hello Helge,
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?
Which project are we speaking of? I'm really overwhelmed right now but maybe I
could find some time to
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
6 matches
Mail list logo
