The errors which I get in Oxygen with both Lisa's document
and a valid TEI XML document from Dr. Becke are quite
different. For example with Dr. Becke's document I get the
following error from Apache FOP (Oxygen's built-in FO
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.
I agree that FOP is not a complete XSL-FO processor and that
the TEI XSL-FO stylesheets which generate the input of the
XSL-FO processor do not handle some constructs very well,
for example the <group> element. You have the option to
configure any other XSL-FO processor as an external FO
transformer in Oxygen and set it up in a transformation
scenario but you need a separate license for the FO
transformer. To configure an external FO transformer
(RenderX XEP, Antenna House XSL Formatter, etc) just specify
the command line that invokes the FO processor from Options
-> Preferences -> XML -> XSLT/FO/XQuery -> FO Processors. If
you want to investigate the issue any further maybe you can
contact us at support [at] oxygenxml [dot] com.
McAulay, Elizabeth wrote:
> Hi All,
> I've had the same problems using the oXygen feature for TEI P5 to PDF
> transformation. I'm attaching my full TEI P5 file. Dr. Becke's errors
> are similar to the errors I got.
> Thanks for any guidance.
> Best regards,