Sebastian Rahtz schrieb:
> Unfortunately, there are four separate things happening
> 1. (trivially), the transformation scenario in oXygen is set up
> to use teiCustom.xsl, which I do not supply; so this is a bit
> confusing. luckily, it does not affect us here, as it involves table
> handling handling.
> 2. the PDF creation works by transforming TEI XML to XSL FO
> and then running a FO prcessor to write PDF. Unfortunately,
> the open source FO processor called FOP, used in oXygen,
> is neither complete nor conformant
> 3. the error messages coming back which you quote are not
> at all the same as I get when I run oXygen, or FOP by hand.
> 4. my TEI to XSL FO stylesheets are not that sophisticated; so
> your TEI file which makes use of <group> does not give
> a sensible output (if you ever get that far!)
> of these, #1 does not matter; #2 means that I do not regard
> this process as seriously viable; #3 I think I have to leave to
> my friends in SyncroSoft; #4 could be solved, but its not
> something I personally am likely to work on in the near future.
> Elizabeth McAulay's problems are related, but not the
> same. Your file generates an empty <fo:flow>, which FOP
> believes is an error (other processors do not), which is caused
> by #4 above. Elizabeth's file fails because it uses figures,
> and FOP cannot handle floats (#2 above).
> Conclusion: I believe my XSL is doing the right thing
> as far as it goes, but it is a bit too simplistic to handle
> your test file.
> Recommendation: if you want results now, generate
> HTML and load it into OpenOffice, and export PDF from that.
thanks for your detailed explanations. i have tested your proposal.
unfortunately it doesn't work the way i hoped. i suppose that the
html-stylesheet doesn't process the page-break-element in a way that it
can be converted using the oo-feature to achieve pdf-files. my idea is
to display the original pagination of the print edition which is the
document to be annotated. but, whatsoever, thanks for your support.