Hi, Could you provide a test case?
As I understood you did something like this: - take a ppt file with a text. - programmatically change the text using HSLF API - save file - style information is wrong after save. Is it correct? Yegor TPN> Hi List, TPN> When PowerPoint stores text in Unicode a unknown char (byte value = TPN> 0) is placed between every "normal" char making the text 2 times longer TPN> than it really is. I can ignore these garbage chars, but I lost the text TPN> style informations, as it's indexes are based in the original unicode TPN> text with all that unicode trash. :( TPN> Is there any way to keep the style information and get the text as a TPN> TextByteAtom, instead of TextCharsAtom? TPN> Thank you very much. TPN> -- TPN> Tales Paiva TPN> --------------------------------------------------------------------- TPN> To unsubscribe, e-mail: [EMAIL PROTECTED] TPN> Mailing List: http://jakarta.apache.org/site/mail2.html#poi TPN> The Apache Jakarta Poi Project: http://jakarta.apache.org/poi/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] Mailing List: http://jakarta.apache.org/site/mail2.html#poi The Apache Jakarta Poi Project: http://jakarta.apache.org/poi/
