Thanks All, I got the latest POI bits and indeed it fixes this issue, at least for chars 32 - 255. It doesn't properly encode chars 0 through 31, though, and I get this:
Invalid character entity reference  Basically, it needs to be  instead. Easy enough to deal with on my end though. Thanks again. Marc On Fri, Oct 14, 2011 at 4:05 AM, Alex Geller <[email protected]> wrote: > An afterthought: There is a thread on this > (http://apache-poi.1045710.n5.nabble.com/Apache-POI-3-8-SXSSFWorkbook-Unreadable-Content-td4658852.html#a4662281) > and the character 160 (non breaking space character) is specifically > mentioned in that thread. According to the thread, the issue was fixed in > build r1154323 so you should not get the issue in 3.8 beta 4. Are you > perhaps referring to the "Big Grid Demo" when saying "streaming API". That > may still have that problem but in SXSSF you should not have this issue > anymore. > Regards, > Alex > > -- > View this message in context: > http://apache-poi.1045710.n5.nabble.com/Creating-XML-Safe-XLSX-Files-via-the-streaming-API-tp4900642p4901778.html > Sent from the POI - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
