Bug 46194 - Unresolved id reference for <fo:wrapper>
Summary: Unresolved id reference for <fo:wrapper>
Status: CLOSED FIXED
Alias: None
Product: Fop - Now in Jira
Classification: Unclassified
Component: pdf (show other bugs)
Version: 0.95
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: fop-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-12 04:03 UTC by Dmitry Beloborodov
Modified: 2012-04-01 06:36 UTC (History)
0 users



Attachments
FO file (62.37 KB, text/plain)
2008-11-12 04:03 UTC, Dmitry Beloborodov
Details
PDF file (52.29 KB, application/pdf)
2008-11-12 04:03 UTC, Dmitry Beloborodov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry Beloborodov 2008-11-12 04:03:09 UTC
Created attachment 22858 [details]
FO file

I'm using DocBook XSL 1.73.2 with FOP 0.95. When I generate a PDF, FOP warns about unresolved ID references, such as this warning:

   /WARNING: Page 9: Unresolved id reference "d0e33" found./

And the page numbers in the index (see "Index" in the FopErr.pdf) for the chapters and appendixes are missing.

The index entry for the section in the FO file looks like:

<fo:page-sequence ...>
<fo:flow ...>
<fo:block ...>
...
<fo:wrapper id="d0e21"> <!-- Change, address --> </fo:wrapper> ...
</fo:block>
</fo:flow>
</fo:page-sequence>

The index entry for the chapter and appendix looks like:

<fo:page-sequence ...>
<fo:flow ...>
...

<fo:wrapper id="d0e33"> <!-- Interface --> </fo:wrapper>

...
</fo:flow>
</fo:page-sequence>

As you can see, the nesting level of index entry for the section differs from the nesting level of index entry for the chapter and appendix.
How can I solve this problem?

FopErr.fo and FopErr.pdf files that demonstrate problem.
Comment 1 Dmitry Beloborodov 2008-11-12 04:03:34 UTC
Created attachment 22859 [details]
PDF file
Comment 2 Andreas L. Delmelle 2008-11-12 09:10:10 UTC
(In reply to comment #0)

Hi

> I'm using DocBook XSL 1.73.2 with FOP 0.95. When I generate a PDF, FOP warns
> about unresolved ID references, such as this warning:
> 
>    /WARNING: Page 9: Unresolved id reference "d0e33" found./

This issue does not exist anymore in FOP Trunk. The "id" property for fo:wrappers that are direct flow-children is not correctly processed in 0.95 and earlier, since those wrappers are completely ignored.
Solved in FOP Trunk as of: http://svn.apache.org/viewvc?view=rev&revision=654111

Workaround for earlier versions would be to use an empty fo:block instead of a fo:wrapper.
Comment 3 Glenn Adams 2012-04-01 06:36:08 UTC
batch transition pre-FOP1.0 resolved+fixed bugs to closed+fixed