[ http://nagoya.apache.org/jira/browse/XERCESJ-1027?page=comments#action_55139 ]
     
Chris Hubick commented on XERCESJ-1027:
---------------------------------------

Please close this bug as INVALID and accept my sincerest appologies for the trouble.

I was passing on this information based on a bug report of my software (uses Xerces) 
given to me by a colleague from a trusted user.  It turns this user was confused, and 
that it was in fact XML Spy which was refusing to validate her XML language codes.  I 
should have double checked myself, but instead wen't looking for a cause, and finding 
the RFC updates covering exactly the reported issue, made an assumption that it was a 
correct bug report.  Sorry.


> Support RFC 3066 language codes
> -------------------------------
>
>          Key: XERCESJ-1027
>          URL: http://nagoya.apache.org/jira/browse/XERCESJ-1027
>      Project: Xerces2-J
>         Type: Bug
>   Components: XML Schema datatypes
>     Versions: 2.6.2
>     Reporter: Chris Hubick

>
> XML instance documents with 'Language' datatype values containing RFC 3066 compliant 
> three letter language codes (tags) will not validate with Xerces.
> Background:  The old XML Schema datatypes document
> http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#language
> referenced RFC 1766, as did the core XML 1.0 Second Edition specification.  XML 1.0 
> Third Edition, and the new XML Schema specification both now reference the newer RFC 
> 3066.  I understand the major change is that RFC 3066 supports the three letter 
> language tags from ISO 639.
> http://www.w3.org/TR/REC-xml/#sec-lang-tag
> http://www.w3.org/TR/xmlschema-2/#language
> http://www.ietf.org/rfc/rfc3066.txt

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

Reply via email to