Return-Path: X-Original-To: apmail-incubator-ooo-issues-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 28CD39CC0 for ; Tue, 17 Apr 2012 18:07:53 +0000 (UTC) Received: (qmail 23297 invoked by uid 500); 17 Apr 2012 18:07:53 -0000 Delivered-To: apmail-incubator-ooo-issues-archive@incubator.apache.org Received: (qmail 23276 invoked by uid 500); 17 Apr 2012 18:07:53 -0000 Mailing-List: contact ooo-issues-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-issues@incubator.apache.org Delivered-To: mailing list ooo-issues@incubator.apache.org Received: (qmail 23267 invoked by uid 99); 17 Apr 2012 18:07:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Apr 2012 18:07:53 +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.123] (HELO sif.zones.apache.org) (140.211.11.123) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Apr 2012 18:07:49 +0000 Received: by sif.zones.apache.org (Postfix, from userid 80) id AE39D42EC; Tue, 17 Apr 2012 18:07:28 +0000 (UTC) From: bugzilla@apache.org To: ooo-issues@incubator.apache.org Subject: DO NOT REPLY [Bug 3395] Reveal formatting codes Date: Tue, 17 Apr 2012 18:07:16 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Word processor X-Bugzilla-Component: formatting X-Bugzilla-Keywords: rfe_eval_ok, usability X-Bugzilla-Severity: trivial X-Bugzilla-Who: orcmid@apache.org X-Bugzilla-Status: ACCEPTED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: andreas.martens@oracle.com X-Bugzilla-Target-Milestone: OOo Later X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: https://issues.apache.org/ooo/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 https://issues.apache.org/ooo/show_bug.cgi?id=3395 --- Comment #160 from orcmid 2012-04-17 18:07:16 UTC --- Created attachment 77455 --> https://issues.apache.org/ooo/attachment.cgi?id=77455 Extracts of the ODF document showing how the same text shown in attachment #77454 is formatted in ODF via an OpenOffice-lineage application I should point out that the exercise for making a roundtrip from WPD to ODT to WPD was done using LibreOffice 3.3.2 as the intermediary. It formats ODT output in the same way as all OpenOffice.org 3.x implementations do, including the forthcoming Apache OpenOffice 3.4. There are two parts in the XML specimen. The first, the element provides the text of the single paragraph in the document. It is this: This little ditty is simply to see what Reveal Codes is all about when used in Word Perfect . Notice that, although no specific style was selected with this document, a number of automatic styles are applied based on actions taken by the document author (mainly font selections, bolding, italicizing, and changes of font size). THe different elements and their text:style-name attributes appeal to the places where the resulting formatting conditons have been retained. Note that there is an automatic style for the paragraph itself as well. Here is one of the automatic style definitions (all of them are in the attached file). They are all on this pattern: These are not done in a way where only the change from the adjacent span is handled, nor are spans nested in a way that has inner spans only identify changes. It is of course possible to synthesize such information -- it was done when the ODT was converted back to a WPD. But it is not how the OpenOffice-lineage engines are designed to reflect certain format changes via introduction of automatic styles that capture them. In addition, for someone working natively with OpenDocument format documents, any kind of Reveal Styling (it is not about codes) would need to be more harmonious with how the format works as well as the different ways the format can be controlled by user actions (i.e., using some sort of Reveal Styling to see where to adjust the document in the editor or in the Reveal Styling interface itself). Having said all of those high-level things, there is also this: There was in the past a macro that managed to do a reasonable job at providing style information about selected text in OpenOffice.org. There is information about that in the comments on this issue. That remains the most-likely-achievable expedient solution and it depends on someone able and willing to recover and continue that work, if not re-invent it. (In reply to comment #154) > I have a couple of examples that might at least clarify how different the > situations are. I wonder how many more years this request will still be here! (In reply to comment #158) > I find it interesting that OpenOffice.org-lineage programs tend to create flat > switching among automatically-created anonymous styles within a paragraph or > heading, without any tendency to do nesting. That does not mean it > is difficult to translate. OpenOffice.org 3.3 accepts WPD files and produces > ODT files in its way of styling. WordPerfect X5, I see, accepts the ODT file > and after conversion manages to place it in its format structure, as can be > seen in the Reveal Codes of the ODT->WPD conversion. -- Configure bugmail: https://issues.apache.org/ooo/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.