OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [docbook-apps] FOP compatibility status? 0.70.1 qandaset + FOP 0.20.5 = :(


----- Original Message ----- 
From: "Dan Sanderson" <lists@dansanderson.com>
To: <docbook-apps@lists.oasis-open.org>
Sent: Tuesday, December 05, 2006 3:59 PM
Subject: [docbook-apps] FOP compatibility status? 0.70.1 qandaset + FOP 
0.20.5 = :(


> Hi all -
>
> So I've run into the FOP 0.20.5 bug where DocBook's qandaset, through 
> DocBook XSLT 0.70.1, sometimes causes FOP to throw an oddball "The id 
> "xxx" already exists in this document".  This appears to have been 
> reported as FOP bug 14962:
>
> http://issues.apache.org/bugzilla/show_bug.cgi?id=14962
>
> The bug was resolved as "fixed in 0.90alpha", and no updates were made to 
> the 0.20.5 branch.  The "latest" branch for FOP is up to 0.92beta.
>
> I can't get simple books to build with FOP 0.92beta, but recent traffic 
> on this list implies some people have been successful with it.  Is XSLT 
> 0.70.1 expected to work with FOP 0.92beta?  Is 0.71.1?

I presume you mean 1.70.1 and 1.71.1 for the stylesheets.  Yes, they work 
with FOP 0.92beta, but the FOP beta is not bug free.  I find that some 
documents process and others don't.  I think that's just because it is 
unfinished.

> Or are only the DB5 templates working with the latest FOP at this time?

If you mean the experimental DB5 stylesheets that I made available 
recently, they are really no different from the standard 1.71.1 templates 
except they expect a namespace prefix on element names.

> Is it generally accepted that the DB4 templates and FOP 0.20.5 together 
> do not provide a usable implementation for qandaset?  Or am I missing 
> something?

I guess that is the case, unless someone else has a workaround for this 
problem.  The qanda templates use an ordinary fo:list-block for qandaset 
and fo:list-item for formatting each qandaentry, and those FO elements are 
used in many other templates as well.  You could try rewriting the 
templates to use an fo:table instead.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]