Mark Hall wrote: > And so I have done :-). The RtfImage class has been updated and two settings > added in the RtfDocumentSettings to control the image output. I've also > updated the documentation.
Just tried it and it works nicely. Thanks a lot! :) >> I noted that you convert the raw image data to rtf format when constructing >> the RtfImage object, why don't you encode while writing? Could save quite a >> bit of memory. Or even better: Why not just write the binary image data >> using the \bin keyword? > There is no real reason. Throughout my area of the code, I've tried to keep a > separation between extracting the information from the iText core objects and > actually writing that information. Also efficiency isn't at the top of my > list of things to look at. The reason for not writing binary data is that the > RTF spec says that the hex display is the default, so I stuck with that. Well would you mind if I optimized memory usage and added code for optional binary image data output? I.e. would you be willing to apply my changes to your code? Regards, Thomas ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions Buy the iText book: http://itext.ugent.be/itext-in-action/
