Return-Path: X-Original-To: apmail-poi-dev-archive@www.apache.org Delivered-To: apmail-poi-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1C267BA33 for ; Fri, 20 Jan 2012 11:07:12 +0000 (UTC) Received: (qmail 52062 invoked by uid 500); 20 Jan 2012 11:07:11 -0000 Delivered-To: apmail-poi-dev-archive@poi.apache.org Received: (qmail 52013 invoked by uid 500); 20 Jan 2012 11:07:10 -0000 Mailing-List: contact dev-help@poi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "POI Developers List" Delivered-To: mailing list dev@poi.apache.org Received: (qmail 51974 invoked by uid 99); 20 Jan 2012 11:07:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jan 2012 11:07:09 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.115] (HELO eir.zones.apache.org) (140.211.11.115) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jan 2012 11:07:07 +0000 Received: by eir.zones.apache.org (Postfix, from userid 80) id 8B4E64F798; Fri, 20 Jan 2012 11:06:46 +0000 (UTC) From: bugzilla@apache.org To: dev@poi.apache.org Subject: DO NOT REPLY [Bug 52484] Superscript font works for XSSFWorkbook but not SXSSFWorkbook Date: Fri, 20 Jan 2012 11:06:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: POI X-Bugzilla-Component: SXSSF X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: yegor@dinom.ru X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: dev@poi.apache.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: https://issues.apache.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org https://issues.apache.org/bugzilla/show_bug.cgi?id=52484 --- Comment #6 from Yegor Kozlov 2012-01-20 11:06:46 UTC --- In theory we can stream SST too. In this case it wouldn't be a cache of strings - we will simply write out strings and set the SST index in the cell. It is not trivial and will take some time to implement. The starting point is SSTDataWriter which will convert rich text to xml and write into a temp file. The implementation should be similar to SheetDataWriter which does this job for cells and rows. SSTDataWriter should keep track of the last written index and total number of entries in the SST. Next we will tweak SXSSF to delegate string data to SSTDataWriter and update the SST index in the cell. This is something to plan for POI-3.9. Until we release 3.8-final I would stay on the safe side and keep SXSSF as it is. Yegor (In reply to comment #5) > How does the SST differ from the Styles table, which is also maintained in > memory and referenced by the streaming SXSSF? > In other words, whilst SXSSF obviusly couldn't work if all cells were RichText > (because the SST would have to be in memory and SXSSF wouldn't gain you > anything) couldn't it still be beneficial if only a minority of the cells are > RichText? > > We'd need to have an option to tell SXSSF which way to handle RichText, but for > my circumstance it would work (I usually have either huge sheets or fancy > sheets, but I don't know which until after I've started outputting them). -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org For additional commands, e-mail: dev-help@poi.apache.org