Hi all, Before Xerces 2.2.0 was released, we tried to fix a bug in the JAXP code, so that file paths (got from File objects) can be correctly converted to URI's. Thanks to Neeraj, who committed the fix that solved a big part of the problem.
One thing was missing from Neeraj's fix: it doesn't support non-ASCII characters. This is why I committed another fix for the same problem, using a different approach (borrowed from other parts of Xerces), with the support of non-ASCII characters. As we all know, JAXP is not our (Xerces') code, so it's better if it lives in a common place (xml-commons would be a good candidate) so that other projects can have access to this fix. Before moving on, we'll need to pick one of the two solutions. I don't know which one is more appropriate, so I would like to ask for your opinions (especially Neeraj's) on: 1. How long and how much effort does it take to update Neeraj's approach to support non-ASCII characters? 2. In terms of correctness and completeness, in which approach do people feel more confident? 3. Which one performs better? Thanks, Sandy Gao Software Developer, IBM Canada (1-905) 413-3255 [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
