Is there a LOG file when Docs are generated for Derby using ANT?

[Laura Stewart <sc...@gmail.com>]

When I use ANT to generate output for the Derby Documentation, the
command line window shows some errors or issues, such as:

[fop] [INFO] area contents overflows area in line

[fop] [ERROR] Could not load external SVG: Content is not allowed in prolog.

[fop] [ERROR] Error while creating area : No ImageReader for this type
of image (file:/C:/Authoring/Derby/Checks/Derby2373/docs/trunk/out/devguide/appauth_os.jpg)


Is there a log file that gets created for these errors?  I'd like to
look into correcting them.
-- 
Laura Stewart

Re: Is there a LOG file when Docs are generated for Derby using ANT?

[Andrew McIntyre <mc...@gmail.com>]

On 2/28/07, Laura Stewart <sc...@gmail.com> wrote:
> On 2/28/07, Andrew McIntyre <mc...@gmail.com> wrote:
> > If you're wondering whether or not you can get more verbose debug info
> > in the log, you can try adding the line messagelevel="debug" to the
> > dita.fo2pdf target in ditatargets.xml of the DITA toolkit.
>
> And will this provide more debug info in the cygwin window?  Or in the log file
> that I specify with ant tools > ant_tools.out ?

What ends up in ant_tools.out would be the same as what goes by on the
screen if the output is not redirected. Presumably there would be more
information, although I don't know what additional output would be
provided by FOP.

Taking a look at the errors:

[fop] [INFO] area contents overflows area in line

This is caused by malformed FO, a fix would most likely need to be
made in the DITA transforms. Extra debug info would be good here, e.g.
if we knew what the area content was that overflowed, we could inspect
the corresponding FO and determine what is causing the problem.

[fop] [ERROR] Could not load external SVG: Content is not allowed in prolog.

This is also malformed FO, graphics should not be referenced in the FO
prolog, which contains the page layout masters and bookmark tree, only
in the body of the FO. This is probably an error in our
dita2fo-shell.xsl. If we could get the URL or the part of the prolog
where this is being referenced incorrectly we could fix this.

[fop] [ERROR] Error while creating area : No ImageReader for this type
of image (file:/C:/Authoring/Derby/Checks/Derby2373/docs/trunk/out/devguide/appauth_os.jpg)

Is this with FOP 0.93? This seems like a classpath issue, as FOP
should have support for JPEG images built-in. Do you have the
xmlgraphics-commons jar on your classpath?

FWIW, it might be worth it to embed the EPS instead of the JPEG, as
long as the EPS has a good preview bitmap, otherwise it'll look great
when you print it out, but it won't show up in Acrobat. Something to
think about later.

andrew

Re: Is there a LOG file when Docs are generated for Derby using ANT?

[Laura Stewart <sc...@gmail.com>]

On 2/28/07, Andrew McIntyre <mc...@gmail.com> wrote:
> If you're wondering whether or not you can get more verbose debug info
> in the log, you can try adding the line messagelevel="debug" to the
> dita.fo2pdf target in ditatargets.xml of the DITA toolkit.

And will this provide more debug info in the cygwin window?  Or in the log file
that I specify with ant tools > ant_tools.out ?

-- 
Laura Stewart

Re: Is there a LOG file when Docs are generated for Derby using ANT?

[Andrew McIntyre <mc...@gmail.com>]

On 2/28/07, Laura Stewart <sc...@gmail.com> wrote:
> When I use ANT to generate output for the Derby Documentation, the
> command line window shows some errors or issues, such as:
>
> [fop] [INFO] area contents overflows area in line
>
> [fop] [ERROR] Could not load external SVG: Content is not allowed in prolog.
>
> [fop] [ERROR] Error while creating area : No ImageReader for this type
> of image (file:/C:/Authoring/Derby/Checks/Derby2373/docs/trunk/out/devguide/appauth_os.jpg)
>
>
> Is there a log file that gets created for these errors?  I'd like to
> look into correcting them.

If you're wondering whether or not you can get more verbose debug info
in the log, you can try adding the line messagelevel="debug" to the
dita.fo2pdf target in ditatargets.xml of the DITA toolkit.

andrew

Re: Is there a LOG file when Docs are generated for Derby using ANT?

[Andrew McIntyre <mc...@gmail.com>]

On 3/6/07, Kim Haase <Ca...@sun.com> wrote:
> Belatedly expressing interest in this issue -- I'm also noticing a bunch
> of errors with the new FOP jar that didn't appear before. For example:
>
> 1) IDs of the following form now generate an "Unresolved id reference"
> error, and the links no longer work in the PDF (though they do in the
> HTML, both mono and multipage). The syntax of the links and ids seem to
> be perfectly valid.
>
> rrefjta16677.dita:href="rrefjta51021.dita#rrefjta51021/jta75105">javax.transaction.xa.Xid</xref>,</i>
> and <i><xref
> rrefjta51021.dita:<li id="i1018125"><i
> id="jta75105">javax.transaction.xa.Xid<ph><indexterm>javax.transaction.xa.Xid</indexterm></ph></i></li>

FOP may be expecting that these id attributes belong to an <fo:block>
and not a subelement of a block, like an inline or text formatting
element. I'll look into this at some point.

> 2) There are a lot of errors about the "column-number" property, which
> doesn't occur in the DITA source, so it must come from some intermediate
> step that has stopped working. These errors don't seem to affect the
> output (I suppose they apply to tables, but the tables look fine); but
> they are a nuisance.
>
>        [fop] Mar 5, 2007 4:14:48 PM org.apache.fop.fo.PropertyList
> convertAttributeToProperty
>        [fop] SEVERE: Ignoring property: column-number=""
> (file:///C:/javadb/trunk/out/ref/refderby.fo:6067:6751: No conversion
> defined ; property:'column-number')

These are similar to the previous errors we were receiving about
invalid column-numbers, but FOP 0.93 is more verbose with its logging.
Not sure why the column numbers are empty, but its probably a problem
with the DITA toolkit's FO transforms for tables.

andrew

Re: Is there a LOG file when Docs are generated for Derby using ANT?

[Kim Haase <Ca...@Sun.COM>]

Belatedly expressing interest in this issue -- I'm also noticing a bunch 
of errors with the new FOP jar that didn't appear before. For example:

1) IDs of the following form now generate an "Unresolved id reference" 
error, and the links no longer work in the PDF (though they do in the 
HTML, both mono and multipage). The syntax of the links and ids seem to 
be perfectly valid.

rrefjta16677.dita:href="rrefjta51021.dita#rrefjta51021/jta75105">javax.transaction.xa.Xid</xref>,</i> 
and <i><xref
rrefjta51021.dita:<li id="i1018125"><i 
id="jta75105">javax.transaction.xa.Xid<ph><indexterm>javax.transaction.xa.Xid</indexterm></ph></i></li>

2) There are a lot of errors about the "column-number" property, which 
doesn't occur in the DITA source, so it must come from some intermediate 
step that has stopped working. These errors don't seem to affect the 
output (I suppose they apply to tables, but the tables look fine); but 
they are a nuisance.

       [fop] Mar 5, 2007 4:14:48 PM org.apache.fop.fo.PropertyList 
convertAttributeToProperty
       [fop] SEVERE: Ignoring property: column-number="" 
(file:///C:/javadb/trunk/out/ref/refderby.fo:6067:6751: No conversion 
defined ; property:'column-number')

Laura, have you had any luck diagnosing these, or the ones you noticed?

Thanks,
Kim

Laura Stewart wrote:
> When I use ANT to generate output for the Derby Documentation, the
> command line window shows some errors or issues, such as:
> 
> [fop] [INFO] area contents overflows area in line
> 
> [fop] [ERROR] Could not load external SVG: Content is not allowed in 
> prolog.
> 
> [fop] [ERROR] Error while creating area : No ImageReader for this type
> of image 
> (file:/C:/Authoring/Derby/Checks/Derby2373/docs/trunk/out/devguide/appauth_os.jpg) 
> 
> 
> 
> Is there a log file that gets created for these errors?  I'd like to
> look into correcting them.

Re: Is there a LOG file when Docs are generated for Derby using ANT?

["Jean T. Anderson" <jt...@bristowhill.com>]

Laura Stewart wrote:
> On 2/28/07, Jean T. Anderson <jt...@bristowhill.com> wrote:
> 
>> No file gets automatically created. I usually output the run to a file,
>> like this on linux:
>>
>>  ant tools >& ant_tools.out
>>
>> on windows, this should do it (anyone, please correct me if I'm wrong):
>>
>>  ant tools > ant_tools.out
>  
> So I would specify ant tools > ant_tools.out before I specify ant pdf.ref ?

If you want to just process the pdf.ref book, do something like this:

  ant pdf.ref > your_log_file

So the basic format is:

  ant product > output_file

The "product" needs to be a target in the build.xml, like "pdf.ref". You
can name the output_file anything you want.

And to increase the level of detail, also do what Andrew suggested:

> If you're wondering whether or not you can get more verbose debug info
> in the log, you can try adding the line messagelevel="debug" to the
> dita.fo2pdf target in ditatargets.xml of the DITA toolkit. 

 -jean

Re: Is there a LOG file when Docs are generated for Derby using ANT?

[Laura Stewart <sc...@gmail.com>]

On 2/28/07, Jean T. Anderson <jt...@bristowhill.com> wrote:
> No file gets automatically created. I usually output the run to a file,
> like this on linux:
>
>  ant tools >& ant_tools.out
>
> on windows, this should do it (anyone, please correct me if I'm wrong):
>
>  ant tools > ant_tools.out

So I would specify ant tools > ant_tools.out before I specify ant pdf.ref ?

-- 
Laura Stewart

Re: Is there a LOG file when Docs are generated for Derby using ANT?

["Jean T. Anderson" <jt...@bristowhill.com>]

Laura Stewart wrote:
> When I use ANT to generate output for the Derby Documentation, the
> command line window shows some errors or issues, such as:
> 
> [fop] [INFO] area contents overflows area in line
> 
> [fop] [ERROR] Could not load external SVG: Content is not allowed in
> prolog.
> 
> [fop] [ERROR] Error while creating area : No ImageReader for this type
> of image
> (file:/C:/Authoring/Derby/Checks/Derby2373/docs/trunk/out/devguide/appauth_os.jpg)
> 
> Is there a log file that gets created for these errors?  I'd like to
> look into correcting them.

No file gets automatically created. I usually output the run to a file,
like this on linux:

  ant tools >& ant_tools.out

on windows, this should do it (anyone, please correct me if I'm wrong):

  ant tools > ant_tools.out

 -jean