> > Also, I'd be happy to work on a patch for this if I get a pointer in the > > right direction. > > The best place to start would be to file (or find) the bug report > and attach a minimal test case (with schema and XML file(s) if > necessary) to it that reproduces the problem.
I can/will, the reason I asked about a place to start was that I thought this was a well known issue from previous discussions, and it's not really a bug per se, just a (IMHO) suboptimal implementation choice. I wasn't even sure that 3.0 still had the problem, but I think it does. If I knew where in the code to look, I'm willing to try and propose a patch rather than just report the issue, that's what I meant by a place to start. -- Scott --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
