I ran into precisely the same problem with xhtml1-strict with Xerces 2.6.2. I reviewed the errata you indicated--does that mean there is a patch available for Xerces 2.6.2, or that it will be in a future version? What does a casual user do today to get around this bug?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
