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: https://github.com/mquinson/po4a/blob/master/doc/po4a.7.pod#using-po4a This text refers to the documentation of po4a(1) itself, available from: https://po4a.org/man/man1/po4a.1.php In particular, I added a paragraph about the deprecation of the individual scripts that you may find useful: https://github.com/mquinson/po4a/blob/master/doc/po4a.7.pod#why-are-the-individual-scripts-deprecated I think that this closes the current bug (once the fix is integrated to Debian). Please comment if you think otherwise. Thanks for your feedback and support, Mt Le mardi 06 juin 2023 à 18:46 +0200, Helge Kreutzmann a écrit : > 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 work flow we use. The > documentation assumes an intial "run" with a previous translation and > then po4a. (See my report you cite below).
signature.asc
Description: This is a digitally signed message part
