Hi Ken,
I recall a couple of months ago that someone reported a situation exactly
like this. I then verified that Xerces does indeed support UTF-16--if the
document is written according to that encoding--and sent an example doc to
the person reporting the bug. They then took another look on their end and
found that something was wrong with their document.
So let me know if you need an example of a UTF-16 document that Xerces
handles.
Cheers,
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone: 416-448-3519, T/L 778-3519
E-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED] on 09/11/2001 05:48:11 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Why doesn't xerces support UTF-16 encoding?
Hi,
I am trying to use xml with an encoding of "UTF-16". Why doesn't xerces
support "UTF-16" and I am getting the "UTF-16 is not supported" error.
More over, why doesn't xerces have a mapping for "UTF-16" to Java's
encoding? Below is the stack trace I get.
Any explanation would help out a great deal.
Also, the archives list not not working for xercesJ, for users?
Exception in thread "main" com.sybase.DataBean.exception.DataBeanException:
DataBeanOpaque::createDocument JDOM
---->Exception->Error on line 0: The encoding "UTF-16" is not supported. at
com.sybase.DataBean.util.DataBeanOpaque.createDocument(DataBeanOpaque.java:608)
at datatypesxsd.SchemaDatatypes.<init>(SchemaDatatypes.java:74)
at datatypes_client.main(datatypes_client.java:25)
Thanks,
Ken
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
