Java doesn't tend to cope too well (at least not without significant extra effort by the programmer) with stuff outside the BMP. It's probably some sort of bug in JDOM, technically - but I'm not sure about that. It'd be painful to fix.
well, we have a problem of compliance then.
I guess so. I suspect it's one that will _in practice_ only come up in test suites, but in the future it'll be increasingly likely that people will actually want to use 'high' unicode characters.
Do you know how this _should_ be handled? Does the parser have to decompose 𐀀 to a surrogate pair? And then presumably compose that surrogate pair to a single character on serialisation/output (if - as we usually see with webdav - the output is UTF-8)
Anyway, I'd be very surprised if slide were doing anything internally that could break this - so I suppose it must be a parser bug. Probably not a particularly easy one to fix.
Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
