Re: [ERROR] fo:marker must be an initial child,and 'marker-class-name ' must be unique for same parent

On Fri, Sep 19, 2003 at 11:53:03AM +0200, Gisbert Amm wrote:
> Hi Bob,
> 
> I've notized that the error about fo:marker is back with the 1.62.0 XSL.
> 
> (see http://sources.redhat.com/ml/docbook-apps/2002-q3/msg00397.html - "When
> I switch from 1.52.2 to 1.53.0, this error message from fop goes away." and
> http://lists.oasis-open.org/archives/docbook-apps/200207/msg00243.html -
> "The error about the fo:marker was a bug.  I filed it and fixed it in CVS").
> 
> I've tried it with 1.61.0 aswell, and it was already there ...
> 
> I'm still using fop-0.20.4 with java 1.4.2-b28 on SuSE Linux 8.1

I think the problem now is fop-0.20.4.
When I process a document that has just one <section>
element, I get one fo:marker and it is the first
child of its block.  So the FO output seems to be
correct.  Fop 0.20.4 reports that incorrectly as an
error, but fop 0.20.5 does not.  Can you upgrade
to fop 0.20.5?

-- 

Bob Stayton                                 400 Encinal Street
Publications Architect                      Santa Cruz, CA  95060
Technical Publications                      voice: (831) 427-7796
The SCO Group                               fax:   (831) 429-1887
                                            email: