Bug#493007: debian-policy: Please recommend tracking translation status of l10n man pages
On Thu, Jul 31, 2008 at 07:37:15AM +0200, Christian Perrier wrote:
> Quoting Helge Kreutzmann (debian@helgefjell.de):
>
> > + 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.
Frankly, I do not like po4a for manpages. I think we should provide a
simpler solution that provide the warranty above.
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
Reply to: