Hello Mark, On Thu, May 05, 2022 at 04:27:26PM +0100, Mark Hindley wrote: > On Sun, May 01, 2022 at 04:16:33PM -0300, Jesse Smith wrote: > > > The attached Makefile for man/ does not yet work, but I think it's just my > > > limited man page knowledge. > > > > Thank you for putting this together. I'm applying upstream to our 3.05 > > branch. > > I was still having difficulties with the Makefile you committed. There are > some > patches attached which resolve them for me. > > Helge, I am unclear what the po4a option '--msgid-bugs-address "Your Bugmail > <m...@example.com>"' is for. Is it required or should it be set to something > @upstream sysvinit?
Yes. It should be set to some e-mail address wich actually handles bug
reports on strings. This is put into the header of each message file
(pot and po file).
> Jesse, I have suggested making po4a optional. I wonder if some users might not
> want to install and build the translated pages?
Ideally it should be opt out, e.g. for space constraints. Otherwise
uptake may be very slow.
> Any successfully translated manpages are now installed.
Great.
> What do you both think?
> Subject: [PATCH 3/5] Use single rule and make po4a optional (with warning).
>
> This ensures the version in set in the master copy before being translated.
Looks fine.
> Subject: [PATCH 1/5] Fix parsing LANGUAGES: $ needs escaping in Makefile.
Yes, this was my intent, I just had some trouble with the quoting and
hence my hack. Please use.
> Subject: [PATCH 5/5] Use po4a --stamp option to avoid rebuild every time, also
> requires --destdir=./
I did not implement stamp file yet, my status was just to get the work
going, which I achieved, so yes, the stamp part I agree.
For
> -PO4A_OPTS = --previous --srcdir po/ --destdir po/ --no-backups \
> +PO4A_OPTS = --previous --srcdir po/ --destdir ./ --no-backups --stamp \
We have a (larger) problem, not yet adressed. If the original man
pages get updated, how (and when) are man/po/* updated? My intention
was to do this latest at build time (to avoid outdated translations).
Jesse, how do you want this to be done?
Version a)
- You update man page
- You update man/po/*
This could happen by hand or you could have a makefile target which
you call and then commit the results to the git repository
- Whenever translators see the outdated xx.po (e.g. de.po), they pick
it up, translate it and you integrate it (all at theier own pace).
Version b)
- During release, you update man/po/* (and commit the result!)
- Whenever translators see the outdated xx.po (e.g. de.po), they pick
it up, translate it and you integrate it (all at theier own pace).
However, if you decide to release seldom (e.g. once a year) than
translations are at least outdated this time.
> Subject: [PATCH 4/5] Install i10n manpages, if available.
Did not check this in detail, best to try out. I hadn't coded this
part yet.
> Subject: [PATCH 2/5] Remove dummy VERSION.
Yes, this was part of my testing only, not meant for production.
Greetings
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/
signature.asc
Description: PGP signature
