From dev-return-22932-apmail-forrest-dev-archive=forrest.apache.org@forrest.apache.org Tue Mar 07 17:36:51 2006 Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 97559 invoked from network); 7 Mar 2006 17:36:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Mar 2006 17:36:48 -0000 Received: (qmail 47424 invoked by uid 500); 7 Mar 2006 17:36:46 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 47381 invoked by uid 500); 7 Mar 2006 17:36:46 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 47365 invoked by uid 99); 7 Mar 2006 17:36:45 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Mar 2006 09:36:45 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [212.23.3.142] (HELO rutherford.zen.co.uk) (212.23.3.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Mar 2006 09:36:44 -0800 Received: from [82.69.78.226] (helo=[192.168.0.2]) by rutherford.zen.co.uk with esmtp (Exim 4.34) id 1FGg6h-0005pi-1b for dev@forrest.apache.org; Tue, 07 Mar 2006 17:36:23 +0000 Message-ID: <440DC48C.1030808@apache.org> Date: Tue, 07 Mar 2006 17:36:12 +0000 From: Ross Gardler User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@forrest.apache.org Subject: Re: Modifying plugin References: <440D4D87.2010808@apache.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Originating-Rutherford-IP: [82.69.78.226] X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Paul Bolger wrote: >>Firstly, the warning about heading hierarchy. This warning is there for >>a reason, in some cases information may be lost if the hierarchy is not >>correct. You need to be very careful if turning it off. However, your >>point is valid and this should really be parameterised, more on this below. > > > Point taken. I'd be interested to know when this would cause > information loss: obviously no one wants that... "Information loss" is not very accurate, I should have said something like "unpredictable behaviour". Here's just one example of such unpredictable behaviour: Consider a TOC built within OOo. It includes all headings of level 1 or 2. If you go from level 1 heading to level 3 heading this will be OK, but in Forrest how is this handled? Does it convert Heading 1 blah blah Heading 3 blah blah to
Heading 1

blah blah

Heading 3

blah blah

or to
Heading 1

blah blah

Heading 3

blah blah

The former will result in heading 3 being in the TOC (which is unintended), the latter will result in yet more unpredictable behaviour since some output formats are incapable of representing sections with no title (such as HTML and XHTML1, but not XHTML2) >>Your point about an "arrow graphic" confuses me. I have never seen this, >>so it is a specific use in your case. Certainly, the samples, such as >>[1], do not exhibit this behaviour. It would be best for us to figure >>out why this is happening and improve the stylesheets to prevent it >>happening when not expected, as in your case. Can you post the code >>snippet you needed to change for this. > > > the relevant line out of the stylesheet (pelt.screen.css) is > > p.instruction { > display: list-item; > list-style-image: url('../themes/images/instruction_arrow.png'); > list-style-position: outside; > margin-left: 2em; > } OK so the graphic is inserted by the stylesheet, not the OOo. But why is your text being marked as an instruction... > in > > openoffice-writer-to-forrest.xsl > > the code was > > > >

> >

> > Ahhh... P2 is defined in the SXW How-To template as an instruction. This is clumsy, it should be a named style not an OOo defiend style (which is P2). We need to change the How-To template document to provide a named style for this and leave the OOo defined style names unnafected by the OOo stylesheet since we have no control over how they are defined. > beats me why it's being triggered by this specific document. The doc > in question originated in MS Word and was translated to sxw by OO 2.0, > and the problem happened across a few docs I was referencing. Just coincindence that some internal MS style has been converted to "P2" in the OOo docs. The above should fix this. Ross That's a problem with the