> You cannot get RC=0 with Apache FOP. That's reassuring :-} I'll concentrate on the actual output and not worry too much about the log unless I can see something wrong. Thanks!
On Fri, Sep 27, 2013 at 6:05 PM, Hussein Shafie <huss...@xmlmind.com> wrote: > On 09/27/2013 04:15 PM, Niels Grundtvig Nielsen wrote: > >> Here are three lines from the command-execution log for converting a >> bookmap to .pdf – I can't spot anything obviously wrong with the output, >> so I'm wondering how to read and understand the warnings. >> >> [FOP INFO] Rendered page #1. >> [FOP WARNING] Line 1 of a paragraph overflows the available area by more >> than 50 points. (See position 283:655) >> [FOP INFO] Rendered page #2. >> > > It's almost always safe to ignore these warnings. > > > > >> I assume from viewing the whole log that the Warning is related to >> rendering the /next /page number in the log: so the example means FOP >> >> has found something to be unhappy about on output page 2. >> Question: what does the warning actually imply for the quality of the >> output document? >> > > The answer is almost always no. > > > > > > I don't see any text overflowing the margins, or any >> truncated content. >> > > Truncated content is normal when a FOP has to render a no-wrap text line > which is wider than the page. This sometimes happens when processing <pre> > elements or a table cell containing a long URL. > > > > > >> Thanks for any advice on this: it's always more satisfying to run a job >> and get an RC of zero :-} >> >> > You cannot get that with Apache FOP. > >
-- XMLmind XML Editor Support List xmleditor-support@xmlmind.com http://www.xmlmind.com/mailman/listinfo/xmleditor-support
