Sorin Ristache wrote:
> For example with Dr. Becke's document I get the following error from
> Apache FOP (Oxygen's built-in FO processor):
> Error(1/-1): fo:flow is missing child elements. Required Content
> Model: marker* (%block;)+
> Dr. Becke's error ("The process 'FOP' ended with code: 1. The error
> was: USAGE
> Fop [options] [-fo|-xml] infile [-xsl file] ...") is obtained only
> when FOP is invoked with wrong parameters which should never happen
> with the predefined transformation scenario "TEI P5 PDF" which you
> said you used.
yes, this is the odd one. I don't understand it either.
the "fo:flow is missing child elements" is indeed simply because the XSL
does not understand <group>
Information Manager, Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431