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:
> 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,

Thanks for the update.

Based on what is in git now (I just updated the German translation)
this is now described quite well for the standard package. And yes, so
this bug can be closed when 0.70 (?) hits unstable.

Not related to this bug, but the basis for my bug report:
The workflow using po4a is appears quite orthogonal to manpage-l10n
needs. I could roughty conceive how (parts of) such an implemenation
could look like. So if 2030 comes closer and the depreciation is not
lifted, I might need to work this out and hope that it both works and
the runtime is not too bad.

Greetings and thanks for maintaining po4a

           Helge
-- 
      Dr. Helge Kreutzmann                     deb...@helgefjell.de
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

Attachment: signature.asc
Description: PGP signature

Reply via email to