You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-users@xmlgraphics.apache.org by Steve Fogel <ST...@oracle.com> on 2010/11/18 03:19:47 UTC
How to tell line# in input file that is generating error
Hi, all.
With Apache FOP 0.95 (the one that comes with the DITA Open Toolkit), I'm getting many error messages like this:
[fop] Nov 17, 2010 3:58:21 PM org.apache.fop.fo.properties.LengthRangeProperty checkConsistency
[fop] SEVERE: forcing opt to min in LengthRange
How can I tell which line # in the FO input file is generating the error? I've tried debug mode and verbose mode, but neither seems to do much. Any tricks?
Thanks
Steve
P.S. - I know what the message means. It's just that my FO input file is over 50K lines, so it's hard to find the culprit.
--
HYPERLINK "http://www.oracle.com/" \nOracle
Steve Fogel | Information Architect, Oracle Database
Phone: +1 6505064914 | Mobile: +1 4153098660
500 Oracle Parkway, M/S 4op1126 | Redwood Shores, CA 94065
HYPERLINK "http://www.oracle.com/commitment" \nGreen Oracle
Oracle is committed to developing practices and products that help protect the environment
Re: How to tell line# in input file that is generating error
Posted by daveg <gr...@gmail.com>.
This solution worked for me.
I was staring at those attributes in the commons-attr.xsl file wondering if, and
what, id have to do to these attributes to fix the problem, then I found your
reply! thanks a lot! I've had to sort out reams of errors and this was the last
one so thanks again.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: How to tell line# in input file that is generating error
Posted by ALI <ac...@yahoo.fr>.
Hi Steve
I found a solution to your problem.
En fact in demo/fo/cfg/fo/attrs/commons-attr.xsl file the <p> properites are
bad :
<xsl:attribute name="space-after">0.6em</xsl:attribute>
<xsl:attribute name="space-after.optimum">3pt</xsl:attribute>
space-after == space-after.minimum.... so there are two incompatible values
I try
<xsl:attribute name="space-after">0.6em</xsl:attribute>
<xsl:attribute name="space-after.optimum">0.6em</xsl:attribute>
which may succeed.
Enjoy
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: How to tell line# in input file that is generating error
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Hi Steve
Unfortunately, not all of FOP's error messages have the ability to
report line numbers. The one you're seeing is a simple log message. So
there is currently no way to display a line number even if the XSLT
processor were able to supply the correct line number (using SAX's
Locator interface).
Essentially, you have to scan your FO/XSLT for uses of the .minimum and
.optimum subproperties. Apparently, you're setting .optimum to a smaller
value than .minimum in some places.
On 18.11.2010 17:12:06 Steve Fogel wrote:
> Hi.
>
> Restating the question: Is there an option I can set that will have FOP
> either print out a line # with this range error message, or print out
> the FO input file as it processes it along with error messages so I can
> see where the errors occur?
>
> Thx for your reply. I am already doing what you suggest: Getting the
> intermediate FO-only file and passing it through FOP. These range error
> messages come out, but no line numbers are associated with them so
> there's no way to tell which FO's in the file are causing them.
>
> There are 100's of occurrences of the following in FOP 0.95
>
> [fop] Nov 17, 2010 3:58:21 PM org.apache.fop.fo.properties.LengthRangeProperty checkConsistency
> [fop] SEVERE: forcing opt to min in LengthRange
> Thanks!!
>
> Steve
<snip/>
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: How to tell line# in input file that is generating error
Posted by Ali <ac...@yahoo.fr>.
Hi Steve,
do you have found the problem ? I have the same in dita OT and don't succeed to
resolve it. If you have clues I'm interested.
Thanks
Regards
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
RE: How to tell line# in input file that is generating error
Posted by Steve Fogel <ST...@oracle.com>.
Hi.
Restating the question: Is there an option I can set that will have FOP either print out a line # with this range error message, or print out the FO input file as it processes it along with error messages so I can see where the errors occur?
Thx for your reply. I am already doing what you suggest: Getting the intermediate FO-only file and passing it through FOP. These range error messages come out, but no line numbers are associated with them so there's no way to tell which FO's in the file are causing them.
There are 100's of occurrences of the following in FOP 0.95
[fop] Nov 17, 2010 3:58:21 PM org.apache.fop.fo.properties.LengthRangeProperty checkConsistency
[fop] SEVERE: forcing opt to min in LengthRange
Thanks!!
Steve
--
HYPERLINK "http://www.oracle.com/" \nOracle
Steve Fogel | Information Architect, Oracle Database
Phone: +1 6505064914 | Mobile: +1 4153098660
500 Oracle Parkway, M/S 4op1126 | Redwood Shores, CA 94065
HYPERLINK "http://www.oracle.com/commitment" \nGreen Oracle
Oracle is committed to developing practices and products that help protect the environment
From: Peter Hancock [mailto:peter.hancock@gmail.com]
Sent: Thursday, November 18, 2010 2:49 AM
To: fop-users@xmlgraphics.apache.org
Subject: Re: How to tell line# in input file that is generating error
Hi Steve,
I am not familiar with the DITA Open Toolkit, but to get line numbers you need to explicitly pass fo to FOP and not the combination of xml and the xslt that FOP initially transforms to fo. Maybe DITA provides a way to get the intermediate fo so that you can run it through fop yourself.
Pete
On Thu, Nov 18, 2010 at 2:19 AM, Steve Fogel <HYPERLINK "mailto:STEVE.FOGEL@oracle.com"STEVE.FOGEL@oracle.com> wrote:
Hi, all.
With Apache FOP 0.95 (the one that comes with the DITA Open Toolkit), I'm getting many error messages like this:
[fop] Nov 17, 2010 3:58:21 PM org.apache.fop.fo.properties.LengthRangeProperty checkConsistency
[fop] SEVERE: forcing opt to min in LengthRange
How can I tell which line # in the FO input file is generating the error? I've tried debug mode and verbose mode, but neither seems to do much. Any tricks?
Thanks
Steve
P.S. - I know what the message means. It's just that my FO input file is over 50K lines, so it's hard to find the culprit.
--
HYPERLINK "http://www.oracle.com/" \nOracle
Steve Fogel | Information Architect, Oracle Database
Phone: +1 6505064914 | Mobile: +1 4153098660
500 Oracle Parkway, M/S 4op1126 | Redwood Shores, CA 94065
HYPERLINK "http://www.oracle.com/commitment" \nGreen Oracle
Oracle is committed to developing practices and products that help protect the environment
---------------------------------------------------------------------
To unsubscribe, e-mail: HYPERLINK "mailto:fop-users-unsubscribe@xmlgraphics.apache.org"fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: HYPERLINK "mailto:fop-users-help@xmlgraphics.apache.org"fop-users-help@xmlgraphics.apache.org
Re: How to tell line# in input file that is generating error
Posted by Peter Hancock <pe...@gmail.com>.
Hi Steve,
I am not familiar with the DITA Open Toolkit, but to get line numbers you
need to explicitly pass fo to FOP and not the combination of xml and the
xslt that FOP initially transforms to fo. Maybe DITA provides a way to get
the intermediate fo so that you can run it through fop yourself.
Pete
On Thu, Nov 18, 2010 at 2:19 AM, Steve Fogel <ST...@oracle.com> wrote:
> Hi, all…
>
>
>
> With Apache FOP 0.95 (the one that comes with the DITA Open Toolkit), I’m
> getting many error messages like this:
>
>
>
> [fop] Nov 17, 2010 3:58:21 PM
> org.apache.fop.fo.properties.LengthRangeProperty checkConsistency
>
> [fop] SEVERE: forcing opt to min in LengthRange
>
>
>
> How can I tell which line # in the FO input file is generating the error?
> I’ve tried debug mode and verbose mode, but neither seems to do much. Any
> tricks?
>
>
>
> Thanks
>
>
>
> Steve
>
>
>
> P.S. – I know what the message means. It’s just that my FO input file is
> over 50K lines, so it’s hard to find the culprit.
>
>
>
> --
> [image: Oracle] <http://www.oracle.com/>
> Steve Fogel | Information Architect, Oracle Database
> Phone: +1 6505064914 | Mobile: +1 4153098660
> 500 Oracle Parkway, M/S 4op1126 | Redwood Shores, CA 94065
>
> [image: Green Oracle] <http://www.oracle.com/commitment>
>
> Oracle is committed to developing practices and products that help protect
> the environment
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>