On Sun, Sep 02, 2007 at 11:31:45PM +0100, Colin Watson wrote: > On Sun, Sep 02, 2007 at 10:24:43PM +0200, Jens Seidel wrote: > > On Sat, Sep 01, 2007 at 01:02:33PM +0100, Colin Watson wrote: > > > + is an ISO-639 language code, must be encoded with the usual > > > + legacy (non-UTF-8) character set for that language, as shown > > > + by: > > > + <example compact="compact"> > > > +egrep -v '\.|@|UTF-8' /usr/share/i18n/SUPPORTED > > > > You are aware of the fact that some languages such as Vietnamese have a > > 8 bit encoding but do not match this regular expression > > (vi_VN.TCVN TCVN5712-1)? > > Hmm, yes. I'm not sure what to do about Vietnamese at the moment; I > doubt it works properly right now. I'll check it out.
I doubt it too... > > > + the <tt>fr_BE.UTF-8</tt> locale). It is therefore not yet > > > + recommended to install pages encoded in UTF-8, but rather to > > > > Maybe it would be a good idea to explain what to do with non supported > > encodings these days. What to do with a Vietnamese page? Installing it > > now UTF-8 encoded into vi.UTF-8/ seems fine to me but you write "not yet > > recommended"! > > Well, that just plain won't work; man won't look there. There are some Yup, I'm aware of it. But once proper support to man-db is added it will work. There should be no need to upload a large amount of packages just to fix manual pages after the man-db transition if this can happen already now. (Or should currently not supported manual pages not be installed at all?) Isn't this the core idea of extenting the policy? To guide the developer what should/will be used once the transition happened? hex-a-hop installs already the Vietnamese and the Bulgarian manpages, both are currently not supported (at least in Etch and according to the changelog also in Sid -- and can be used as a test for you). (I will file a bug for Bulgarian on man-db soon.) Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
