Hi Arnaud,
That's about right, but try putting the -d argument before the doc.fo
and doc.pdf. Hopefully you will get a better debugging message. It
sounds like your .fo file has an unknown object in it, although the
message isn't very helpful. You might want to include your .fo file with
your
I had a similiar problem to this when running an FO file output from MSXML
through FOP. If my memory serves correctly, it was caused by the encoding,
which is UTF-16 by default. You need to set it to UTF-8. This may be because
MSXML by default places some binary data in the first byte or two of
