Hello, I'm running into a nasty little problem with the export*View() methods on Session. It looks like the OutputStream implementation has the encoding part of the xml prolog hardcoded to UTF-8. Thats fine for serializing, but blows up when deserializing if I have any non-ascii content (my app is i18n'd to spanish). I've written a workaround and used my own ContentHandler, but I'm wondering if UTF-8 is big enough for general usage? And besides, I really dont want to have all those javax.xml.transform imports all over the place doing nothing but supporting this workaround.
Thanks, Anton -- View this message in context: http://www.nabble.com/SessionImpl.export*View%28%29-serialize-with-prolog-set-to-UTF-8-tf3376445.html#a9397005 Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
