Helge Kreutzmann

Hello Mike, hello Bernd, how do you suggest to proceed? I really love to resolve the file conflicts with manpages-l10n, and I'm glad to help you with po4a integration; however, your last response is from September 2022, about half a year ago, so I'm unsure what to do next. Greetings Helge

Hello Mike, hello Bernd, how do we want to proceed? Thanks for your reply.

Hello Mike, hello Bernd, ping? Do you think this can be integrated in principle? Please let me know any issues you have. Also if you approve the general idea, translation teams can work on updating their text (can happen in parallel to the inclusion). Thanks!

Hello Mike, hello Bernd, did you have a chance to review the latest version? Any further shortcomings or questions? If you agree with the principles, I suggest I review the original man pages (taking into account Bug 41) and afterwards initiate a call for updated translations to the French and Brazilian Portuguese Teams (I would handle German myself). Since by design my patch is non-intrusive (i.e. does not change anything unless explicitly called) it would be good to commit it and then everyone...

Hello Mike, I added the requested target(s). They are called "update-po" and "pot". The first updates the po files (those used by translators), the second one updates the pot file and is probably not needed, but might help testing. I also worked on the German translation a little bit and prepared the fr.po and pt_BR.po as much as I could (using strings from manpages-l10n). Please review. Once you agree with the fundamental idea I can request the French and Brazilian Portugese teams to update their...

Hello Mike, currently, the build target will not be called automatically, since up to now nothing needed to be done for "building". So in fact, it is not already the case. But to make this more clear, I can of course rename the make target, no problem. For review: This is all new code except that I copied the man/Makefile and made some small additions. Hence the diff is empty, i.e. nothing to compare. So simply extract my tarball and look at the (new) code. Comparing the two make files yields: ---...

Hello Mike, currently, the build target will not be called automatically, since up to now nothing needed to be done for "building". So in fact, it is not already the case. But to make this more clear, I can of course rename the make target, no problem. For review: This is all new code except that I copied the man/Makefile and made some small additions. Hence the diff is empty, i.e. nothing to compare. So simply extract my tarball and look at the (new) code. Comparing the two man pages yields: ---...

Hello Bernd, hello other developers, Essentially it is ready now (except for some small bugs, of course :-)) I attached it. I can be extracted in man/ How it works: I added the generation part as sub directory to man/ and extended man/Makefile such that the localized man pages are generated, updated, cleaned etc. after the static translated man pages. This is supposed to be temporary, in the long run the static ones should be removed. Please note, that for clarity, I copied Makefile to Makefile.new....