You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kim Haase (JIRA)" <ji...@apache.org> on 2007/04/16 23:30:15 UTC
[jira] Reopened: (DERBY-2373) Upgrade documentation PDF builds to
use FOP .93
[ https://issues.apache.org/jira/browse/DERBY-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase reopened DERBY-2373:
------------------------------
I think there may be something not quite right about the way this new version of FOP is working with our toolkit. Ever since it came in, the doc builds have been generating a very large number of error messages. They are all of one of the following seven types:
[fop] Apr 16, 2007 7:29:20 PM org.apache.fop.layoutmgr.PageBreakingAlgorithm updateData2
[fop] WARNING: Part/page 0 overflows the available area in block-progression dimension. (fo:static-content, location: 11/491)
[fop] Apr 16, 2007 7:29:21 PM org.apache.fop.fo.PropertyList convertAttributeToProperty
[fop] SEVERE: Ignoring property: column-number="" (file:///home/pakker/JavaDBbuild/JavaDBtrunk/pakkJavaDB/bld/derby/docs/out/adminguide/derbyadmin.fo:523:788: No conversion defined ; property:'column-number')
[fop] Apr 16, 2007 7:29:24 PM org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm updateData2
[fop] WARNING: Line 1 of a paragraph overflows the available area. (fo:block, location: 551/716)
[fop] Apr 16, 2007 7:29:30 PM org.apache.fop.area.RenderPagesModel checkPreparedPages
[fop] WARNING: Page 22: Unresolved id reference "radminappsclientsecuritytable" found.
[fop] Apr 16, 2007 7:34:14 PM org.apache.fop.fo.flow.TableColumn bind
[fop] WARNING: table-layout="fixed" and column-width unspecified => falling back to proportional-column-width(1)
[fop] Apr 16, 2007 7:35:08 PM org.apache.fop.fo.flow.TableColumn bind
[fop] WARNING: table-layout="fixed" and column-width unspecified => falling back to proportional-column-width(1)
[fop] Apr 16, 2007 7:35:08 PM org.apache.fop.fo.PropertyList convertAttributeToProperty
[fop] SEVERE: Ignoring property: number-columns-spanned="NaN" (file:///home/pakker/JavaDBbuild/JavaDBtrunk/pakkJavaDB/bld/derby/docs/out/getstart/getstartderby.fo:434:1047: No conversion defined NaN; property:'number-columns-spanned')
Some of the errors may have occurred before FOP .93 (possibly the page and paragraph overflow messages).
Most of them appear to have nothing to do with what is in the actual DITA source, as far as I can tell. The only ones that I can decipher at all is the "Unresolved id reference" errors. These are always the result of an xref link to a table within the same DITA file. As far as I can tell, the xref is perfectly correct. For example, in the file src/devguide/cdevconcepts15366.dita, the xref
<xref href="cdevconcepts15366.dita#cdevconcepts15366/cdevconcepts17741"></xref>
points to the following table tag:
<table frame="all" id="cdevconcepts17741">
The effect of this warning is that in the PDF and monohtml, table xrefs don't work, although they work fine in the frames HTML.
With this one exception, however, the generated PDF and monohtml docs look just fine.
I suspect that many of the errors have to do with tables, since they refer to columns. But the attributes "column-number" and "number-columns-spanned" don't occur in DITA, so some intermediate step seems to have gone haywire.
Builds that incur errors take a lot longer, so this is affecting productivity. It would be great if we could figure out what is going on and fix it.
If I should file a new bug instead of reopening this one, please let me know.
> Upgrade documentation PDF builds to use FOP .93
> -----------------------------------------------
>
> Key: DERBY-2373
> URL: https://issues.apache.org/jira/browse/DERBY-2373
> Project: Derby
> Issue Type: Improvement
> Components: Build tools, Documentation
> Affects Versions: 10.3.0.0
> Reporter: Andrew McIntyre
> Assigned To: Andrew McIntyre
> Fix For: 10.3.0.0
>
> Attachments: derby-2373.diff, derby-2373.stat
>
>
> The current doc build uses FOP 0.20.5, which is rather outdated at this point. The documentation build should be updated to use FOP 0.93.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.