At 13:18 24-11-2001, Peter B. West wrote: >My apologies for not having followed this up more doggedly. Through RFC >3066 I found my way to the ISO 639-2 3-letter codes, ISO 639-2/T >(Terminology) and ISO 639-2/B (Bibliographic). > >Fortunately, Section 2.3, Choice of language tag, of RFC 3066 includes: > > 2. When a language has both an ISO 639-1 2-character code and an ISO > 639-2 3-character code, you MUST use the tag derived from the ISO > 639-1 2-character code. > >This is handy, because it resolves the 639-2/T vs. 639-2/B selection >problem. However, it contradicts the XSL spec quoted below. >----------------------------------------- > >So, your two-letter stuff is The Right Stuff after all.
Not necessarily. RFC 3066 covers language selectors ll-CC, and is referenced by MIME, HTML, and XML, so my xml:lang attributes are right. But it only governs things that reference it, and since XSL doesn't... XSL probably *should*, but right now, there's just an irritating incompatibility. Martin Dürst pointed out on the I18N IG that the XSL language and country settings were mainly intended for cases where xml:lang was insufficiently expressive. So the problem isn't that huge. ~Chris -- Christopher R. Maden, Principal Consultant, HMM Consulting Int'l, Inc. DTDs/schemas - conversion - ebooks - publishing - Web - B2B - training <URL: http://www.hmmci.com/ > <URL: http://crism.maden.org/consulting/ > PGP Fingerprint: BBA6 4085 DED0 E176 D6D4 5DFC AC52 F825 AFEC 58DA
msg03504/pgp00000.pgp
Description: PGP signature
