What I think is a document template error

1
I am getting the following error in my logs: Jul 1 10:22:53 127.0.0.1 propersp: WARNING - org.apache.fop.apps.FOUserAgent: Font "ZapfDingbats,normal,700" not found. Substituting with "ZapfDingbats,normal,400". Jul 1 10:22:53 127.0.0.1 propersp: INFO - org.apache.fop.apps.FOUserAgent: An fo:table (See position 1:4359) is wider than the available room in inline-progression-dimension. Adjusting end-indent based on overconstrained geometry rules (XSL 1.1, ch. 5.3.4) Jul 1 10:22:53 127.0.0.1 propersp: WARNING - org.apache.fop.apps.FOUserAgent: Line 1 of a paragraph overflows the available area by 4897 millipoints. (See position 1:15016) Jul 1 10:22:53 127.0.0.1 propersp: WARNING - org.apache.fop.apps.FOUserAgent: Line 1 of a paragraph overflows the available area by 4897 millipoints. (See position 1:16753) Jul 1 10:22:53 127.0.0.1 propersp: WARNING - org.apache.fop.apps.FOUserAgent: Line 1 of a paragraph overflows the available area by 4897 millipoints. (See position 1:18470) Jul 1 10:22:53 127.0.0.1 propersp: WARNING - org.apache.fop.apps.FOUserAgent: Line 1 of a paragraph overflows the available area by 4897 millipoints. (See position 1:20208) This error does not point me into a direction on which of the 25 document templates I have is the culprit. How do I find that out? Regards, Ronald
asked
1 answers
3

It's not an error but a warning. The font one has been around for a while and is not a problem, it's just something that probably shouldn't be exposed. The one about regions overflowing is a result of how your document templates are designed, apparently something does not quite fit in some cases, this might be as simple as a string being too long. That said, the actual result may still look fine.

These warnings are generated by a library we're using and thus have no knowledge of document templates and couldn't give you a template name. You could of course manually generate some documents and see which of the templates generate the overflow warning.

The reason you see things like this now is a result of changes to our logging system, warnings like these used to be invisible in the logs. In cases like these I don't think they are very beneficial though.

answered