Neeraj Bajaj wrote:
> 1. Although Xerces provides a feature to turn on support
> for Java encodings, using this feature makes applications
> dependent on Xerces: attempting to set this feature on
> other parsers would result in exceptions.
Only if they use Java encoding names which
> Andy Clark wrote:
> > I am curious though as to why setting the
> > http://apache.org/xml/features/allow-java-encodings feature is such a
> > tremendous burden?
>
> I also fail to see the reason why we should change the
> default behavior to accept Java encod
in this world.
> But we'd be completely throwing our hands up in despair at the problem if
> we allowed Java encoding names by default as well as IANA names. To my
> mind, the current situation is as good a compromise as we're likely to
> find.
>
> I am cur
Also, the reason for this request is essentially moot
anyway because the Java I18N library already has a mapping
table for IANA names. (Older version of Java didn't have
such a complete table, hence our use of the encoding map.)
So users shouldn't have to use Java encoding names, anyway.
>
s own thing with regard to
encoding names...
>why does Xerces2 limits itself to IANA ? We
>are not completely addressing the problem and solving anything by doing
so.
But we'd be completely throwing our hands up in despair at the problem if
we allowed Java encoding names by default as
> Glenn wrote:
> Actually, the XML spec doesn't require that a processor recognize
> anything other than UTF-8 and UTF-16,
And that's it.
>so we are being quite nice
> in supporting the IANA registered names.
Why are we being less nice ? :-) Why only IANA registered names, when XML 1.0
sp
I agree with Glenn. I think the allow-Java-encoding-names
feature should remain OFF by default.
--
Andy Clark * [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Actually, the XML spec doesn't require that a processor recognize
anything other than UTF-8 and UTF-16, so we are being quite nice
in supporting the IANA registered names. It is also very helpful
of us to provide an option that supports the use of Java encoding
names at all. Or at le
Hi All,
As of right now, Xerces2 doesn't recognize JAVA encoding names
by default. Xerces2 assumes that encoding names *must* be IANA encoding names
and throws fatal error in other cases.
As per XML 1.0 specification,
http://www.w
