[
https://issues.apache.org/jira/browse/DERBY-2627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14128774#comment-14128774
]
Kim Haase commented on DERBY-2627:
----------------------------------
There are now 31 occurrences of this warning in the Admin Guide, mostly for
section cross-references. I haven't checked other manuals. The result is still
non-working links in the PDF.
Problem seems not to be solvable with current tools.
> WARNING involving RenderPagesModel causes incorrect output
> ----------------------------------------------------------
>
> Key: DERBY-2627
> URL: https://issues.apache.org/jira/browse/DERBY-2627
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.2.2.0
> Reporter: Kim Haase
> Labels: derby_triage10_5_2
>
> A warning like the following appears during the PDF generation of most of the
> manuals:
> [fop] May 8, 2007 9:48:43 AM org.apache.fop.area.RenderPagesModel
> checkPreparedPages
> [fop] WARNING: Page 22: Unresolved id reference
> "radminappsclientsecuritytable" found.
> It appears the following number of times for each manual, always at the end
> of the PDF generation.
> adminguide: 1
> devguide: 4
> getstart: 0
> ref: 50
> tools: 21
> tuning: 32
> In all cases the warning concerns a cross-reference to a table. As far as I
> can tell, the cross-reference follows the correct format for a
> cross-reference. For the above warning, for example, the file
> cadminappsclientsecurity.dita contains this cross-reference:
> <xref
> href="cadminappsclientsecurity.dita#cadminappsclientsecurity/radminappsclientsecuritytable"></xref>
> The reference is to the following table within the same file:
> <table id="radminappsclientsecuritytable">
> The effect of this warning is that in the PDF and monohtml, table xrefs don't
> work (that is, if you click on the apparent link, you don't go the table),
> although they work fine in the frames HTML.
> Since this error causes problems in the output, it should be fixed somehow,
> either by correcting the DITA source or by fixing the toolkit in some way.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
