> That not the issue either. The issue is that some of the _original_ > manpages are not up-to-date and poorly written. Whatever process we use, > the translations are not going to be up-to-date either, and probably > full of mistake because the original was unclear.
As far as I know from po4a (Nicolas will correct if needed), the strings in these manpages will anyway be marked as fuzzy, so that translators have to review them. Nicolas, do you confirm? > > > Using po4a guarantees that the translated manpage remains up-to-date > > because changed strings fuzzy the translations and are not used. This > > may result in a translated manpage which is a mix of English and > > another language....which you can decide not shipping with your > > package with a special case of the build system. > > > > > > So, again, are you completely ruling out po4a in either the package > > build system or the "upstream" tarballs build system? > > No, I am not. OK, that makes all this clearer for me. Sorry for having been a little bit "heavy" as we all say in French...:) (surrealistic discussion we have among 3 French-speaking people...:-))) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
