Modifying HSSFCell string values and SST record

All, Basically i have finished implementing rich text support (yaa!) but have come across an interesting quirk. Currently the SST record will grow based on the number of nuique strings in the file, it never colapses (unless i am missing something), so for example if i continually update a

500K patch file for rich text

All, How do we want to handle this patch for the rich text support. The patch is quite large because it includes the pull method patch attached to bug 31906. I dont believe that this mailing list will allow me to send an email with a file that is arround the 500K mark, so this makes reviewing

DO NOT REPLY [Bug 36075] New: - Documentation on how font information is stored in PowerPoint

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36075. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 36075] - Documentation on how font information is stored in PowerPoint

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36075. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

[EMAIL PROTECTED]: Project jakarta-poi (in module jakarta-poi) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project jakarta-poi has an issue affecting its community integration. This issue affects

[EMAIL PROTECTED]: Project jakarta-poi (in module jakarta-poi) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project jakarta-poi has an issue affecting its community integration. This issue affects

DO NOT REPLY [Bug 36075] - Documentation on how font information is stored in PowerPoint

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36075. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 36075] - Documentation on how font information is stored in PowerPoint

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36075. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

Re: 500K patch file for rich text

Definitely 3.0. Do this: cvs tag BEFORE_RICH do patch cvs commit cvs tag AFTER_RICH that should allow review by anyone with cvs diff -r BEFORE_RICH -r AFTER_RICH... -andy Jason Height wrote: All, How do we want to handle this patch for the rich text support. The patch is quite large

Re: Modifying HSSFCell string values and SST record

There should be a coalesce method. However, it shouldn't run by default as it is probably time consuming. Many people would consider extra filesize a happy tradeoff vs memory consumption or processor utilization. It just depends. It might also be good to optionally (this costs more memory)