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, is discouraged. It is NOT an XML "best practice" to rely on Java encoding names. Repeat after me: "XML is *not* a Java technology". Therefore, to allow Java encoding names by default opens the door to cross-platform and cross-language incompatibility problems. The whole point of XML is to enable inter-operability and making the default to allow Java encoding names would build incompatibility into the system. Not a "good thing". Java encoding names only work in Java. IANA encoding names are recognized to work regardless of the development language and are used across the board in other technologies. I want to re-iterate (again) that we're not forbidding the use of Java encoding names. We're only keeping the default as it is which encourages people to use IANA encoding names. It is true that there are people that *have* to use this feature through no fault of their own. But I would argue that the applications that produce documents with Java encoding names are WRONG and we merely provide a workaround for people that need it. Therefore, the default should stay as it is. -- Andy Clark * [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
