I'm starting to suspect the OP and crew are editing the content to fit
the format. If that is the case, it might be worth the time to hack up a
tool which goes to that line in the fo. Failing that the crew is left
pouring over pdfs looking for bad formatting. In this case, in the test
runs I would change the background colour of the region getting the
overflow so the overflowing content shows up better. Or sometimes
truncating the overflow is enough to show the problem. Still pretty
manual though. Use the fo, luke.
Have we seen what sorts of block and regions are involved?
On 03/27/2014 05:51 PM, Luis Bernardo wrote:
It is not possible to get the page number where the overflow happens,
and it would be tricky to implement. When the overflow happens during
line breaking the page breaking has not happened yet so it is not
known at that stage in what page it will happen.
In any case, there are 72 points in an inch so you just have to take
that in consideration when deciding whether to check the overflow
visually.
On 3/27/14, 10:50 PM, natk wrote:
Yes, it is the position in the FO file (as I said in the original
post) but if the page information was available to print in the log
message, that would make fixing this errors so much easier
(especially for those on my team who aren't expert in trawling
through FO files).
Thanks.
On Fri, Mar 28, 2014 at 12:38 AM, rsargent [via Apache FOP] <[hidden
email] </user/SendEmail.jtp?type=node&node=40366&i=0>> wrote:
Isn't that line number in your FO file ?
Sent from my iPhone
> On Mar 26, 2014, at 8:44 PM, natk <[hidden email]
<http://user/SendEmail.jtp?type=node&node=40356&i=0>> wrote:
>
> Is it possible to configure FOP logging to print page number
information?
>
> I get lots of the following messages:
>
> 2014-03-27 13:17:51,072 WARN
> (org.apache.fop.events.LoggingEventListener:97) - Line 1 of a
paragraph
> overflows the available area by more than 50 points. (See
position 344:409)
>
> I can search the fo file at that position, but it would be so
much easier if
> I knew the output page, then I could go straight to that page
and check the
> overflow.
>
>
>
> --
> View this message in context:
http://apache-fop.1065347.n5.nabble.com/logging-page-number-tp40352.html
> Sent from the FOP - Users mailing list archive at Nabble.com.
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
<http://user/SendEmail.jtp?type=node&node=40356&i=1>
> For additional commands, e-mail: [hidden email]
<http://user/SendEmail.jtp?type=node&node=40356&i=2>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
<http://user/SendEmail.jtp?type=node&node=40356&i=3>
For additional commands, e-mail: [hidden email]
<http://user/SendEmail.jtp?type=node&node=40356&i=4>
------------------------------------------------------------------------
If you reply to this email, your message will be added to the
discussion below:
http://apache-fop.1065347.n5.nabble.com/logging-page-number-tp40352p40356.html
To unsubscribe from logging page number, click here.
NAML
<http://apache-fop.1065347.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
------------------------------------------------------------------------
View this message in context: Re: logging page number
<http://apache-fop.1065347.n5.nabble.com/logging-page-number-tp40352p40366.html>
Sent from the FOP - Users mailing list archive
<http://apache-fop.1065347.n5.nabble.com/FOP-Users-f3.html> at
Nabble.com.
