Quoting Helge Kreutzmann ([EMAIL PROTECTED]): > + If a loclized man page for a certain command is provided, it should
s/loclized/localized > + either be up to date or it should be clearly visible that this version > + is outdated (either by a note in the beginning or by showing the > + missing/changed parts in English instead of the target language). > + Where the build system of the localized man page does not provide the > + option to enable this Debian developers and maintainers are asked to > + take this issue to their upstream to resolve. I'm not sure that the policy talks about "Debian developers". It probably talks about package maintainers or so.... I would also recommend turning the "should" to "must" for native packages. It probably needs the following to be included in the Developer's Reference: > + > + If Debian developers themselves provide a framework to support > + localized man pages this framework must fulfill the requirements of > + the previous paragraphs. In this case it is recommended to use po4a > + for localization. > + That latter part probably belongs more to the Developer's Reference. Indeed, a section about po4a and a simple way to setup a framework for localized manpages would be a great addition to it.
signature.asc
Description: Digital signature
