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 --
From: Peter Hancock
[mailto:peter.hanc...@gmail.com] Hi Steve, On Thu, Nov 18, 2010 at 2:19 AM, Steve Fogel <steve.fo...@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. --
|
--------------------------------------------------------------------- To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org