[XXE] FOP warning
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. 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? I don't see any text overflowing the margins, or any truncated content. Thanks for any advice on this: it's always more satisfying to run a job and get an RC of zero :-} -- XMLmind XML Editor Support List xmleditor-support@xmlmind.com http://www.xmlmind.com/mailman/listinfo/xmleditor-support
Re: [XXE] FOP warning
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 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
[XXE] namespaces in XPath
The dtbook.xxe add-on is failing in version 5.7 of the editor, complaining about this line: I see in the change log that that unknown namespaces were previously ignored and now are not, but I am not clear on how to get it to recognize the dtb namespace. It is declared in the usual way using xmlns:dtb at the top of the file. Boris -- XMLmind XML Editor Support List xmleditor-support@xmlmind.com http://www.xmlmind.com/mailman/listinfo/xmleditor-support
Re: [XXE] namespaces in XPath
On 09/27/2013 06:58 PM, Boris Goldowsky wrote: The dtbook.xxe add-on is failing in version 5.7 of the editor, complaining about this line: I see in the change log that that unknown namespaces were previously ignored and now are not, but I am not clear on how to get it to recognize the dtb namespace. It is declared in the usual way using xmlns:dtb at the top of the file. The , , and child elements of a being namespace-aware, suffice to declare xmlns:dtb normally, in the configuration file where these elements are used. However, you have uncovered a bug. While what's above is necessary, it's not sufficient (hence the bug). The workaround is to add xmlns:dtb="XXX" at the top of *all* your configuration files, whether a .xxe file (main file) or a .incl file (module) and to stick to this prefix for your "XXX" namespace (that is, do not use several prefixes for "XXX"). We'll try to fix this bug for v5.8. However, we plan to release v5.8 in a week or so, so may be it's too late. -- XMLmind XML Editor Support List xmleditor-support@xmlmind.com http://www.xmlmind.com/mailman/listinfo/xmleditor-support
