Chris,

I have posted again to the xsl-editors on this.  Here is the text.

----------------------------------------
Eds,

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.

On a related issue, I was spanked by Max for CCing fop-dev on this, 
because of the risk of directing subsequent discussions of the topic on 
fop-dev into the xsl-editors list.  I see that this has happened.

Sorry Max.

Peter


Christopher R. Maden wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> At 05:37 23-11-2001, Peter B. West wrote:
> 
>>In 5.11 the spec. has:
>>
>><country>
>>    A string of characters conforming to an ISO 3166 country code.
>><language>
>>    A string of characters conforming to the ISO 639 3-letter code.
>>
>>In the copies of the references that I have been recovered, ISO 639 is a 
>>2-letter code.  ISO 3166, on the other hand, defines both 2- and 3-letter 
>>country codes.  Is the spec correct here?
>>
> 
> By definition, yes... (-:
> 
> ISO 639 defines both 2- and 3-letter language codes; see <URL: 
> http://www.w3.org/WAI/ER/IG/ert/iso639.htm >.  I actually hadn't noticed 
> that the Recommendation requires the 3-letter form; that's a bit of a 
> bummer since XML itself allows the two-letter form, which means that a lot 
> of my content has things like xml:lang="en-US" in it, which apparently 
> can't just be copied into FO output.
> 
> ~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
> -----BEGIN PGP SIGNATURE-----
> Version: PGP Personal Privacy 6.5.8
> 
> iQA/AwUBO/8UOqxS+CWv7FjaEQK6CgCfXQVR6lUqHHGGvgdhpi8rsGBKEnEAnRON
> oufW5hnO7NsCiSPfl3+706nn
> =Trb5
> -----END PGP SIGNATURE-----
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
> 
> 


-- 
Peter B. West  [EMAIL PROTECTED]  http://powerup.com.au/~pbwest
"Lord, to whom shall we go?"


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to