On Sat, Sep 01, 2007 at 11:00:41AM +0200, Ramón García wrote: > I would prefer to keep the pages in UTF-8 format. It is technically > possible and simple to have different encodings for different > languages (encoding.c has different entries for each language).
Note that I wrote all that code and am intimately familiar with why it's all there. /usr/share/man/es/ *must* remain ISO-8859-1 because many packages other than manpages-es ship files in there; changing it would break compatibility and require lots of packages to change before everything would work again, and is therefore clearly wrong. We can't yet use /usr/share/man/es.UTF-8/ because man-db doesn't support it yet (though I committed the necessary changes to do so to a branch recently). /usr/share/man/es_ES.UTF-8/ is suboptimal because it discounts all the other countries that use Spanish. Thus, this needs a new upstream release of man-db first. I recognise that manpages-es upstream is providing UTF-8 manual pages and recommending their installation in /usr/share/man/es/, but my responsibility is to ensure proper integration of manual pages across all packages and languages in Debian, and thus I need to take a broader view. It's entirely correct to deviate from upstream on this point in order to ensure sensible integration. > However, no solution is useful without coordinating with the > maintainer of manpages-es, which may change encoding at any time. I will write up a clear policy soon to try to avoid this kind of confusion in future. In the meantime, manpages-es is clearly the odd one out here and needs to revert to its previous encoding. This should be relatively easy to arrange; as I said I'll NMU it soon (particularly since the maintainer's e-mail is bouncing). The maintainers of manpages-* need to remember that they are not the only ones shipping manual pages in their language hierarchies, and that they therefore do not unilaterally own those hierarchies. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
