This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
XSL FO : IDs in page-sequence for basic-link ?
- To: docbook-apps at lists dot oasis-open dot org
- Subject: DOCBOOK-APPS: XSL FO : IDs in page-sequence for basic-link ?
- From: Sylvain Amrani <amrani at mail-me dot com>
- Date: Wed, 04 Apr 2001 21:40:24 +0200
- Organization: segmentfault
Hello,
I was wondering why, using FOP, page numbers for chapters aren't
generated in the TOC, but all is fine for sect* and other
"sub-components".
FOP was complaining about not finding the id of my chapters.
So I read the .fo generated with Saxon and see that the id for
components are attributes of `page-sequence' elements, and id for
sections are attributes of `block' elements.
The xsl fo specification says that for the `basic-link' element, the
`internal-destination' attribute specifies the destination flow object
to point to. I think page-sequence isn't a flow object, but block is.
Maybe it's the reason why FOP won't search the id there.
So I modified the style sheet this way and all is running fine :
$ diff ../../xsl/docbook/fo/component.xsl.org ../../xsl/docbook/fo/component.xsl
156,157c156
< <fo:page-sequence id="{$id}"
< hyphenate="{$hyphenate}"
---
> <fo:page-sequence hyphenate="{$hyphenate}"
177a177
> <fo:block id="{$id}">
178a179
> </fo:block>
(a new block element that carries the id attribute encloses the component title)
Tell me if I'm wrong. Maybe all of this is only a FOP limitation.
Sylvain.
------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: docbook-apps-request@lists.oasis-open.org