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, by the way,
i
> 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 encoding names. Xerces2
> does not pre
Hi Neil,
> >Ideally, We should first take user permission before we make any
> >attempt to parse such (other than UTF-8, UTF-16) documents to make sure
> that
> >application/user is aware that by doing so it is tying itself to processor
> based
> >feature and may not obtain the desired result wh
[EMAIL PROTECTED] wrote:
> My own experience with developers and encodings suggests to me that few
> people are very well aware of anything. :-) To my mind, the really
> regrettable problem is that Java chose, at some point in the misty past, to
> part company with W3C, IETF and IANA and do its o
Hi Neeraj,
>Ideally, We should first take user permission before we make any
>attempt to parse such (other than UTF-8, UTF-16) documents to make sure
that
>application/user is aware that by doing so it is tying itself to processor
based
>feature and may not obtain the desired result when shifting
> 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 least I would
