[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [docbook-apps] Whitespace in <indexterm>
Bob, thanks very much for investigating this behavior and following up with us. Best, Steve Blair Director of Technical Publications Vocera Communications sblair@vocera.com 408.790.4210 -----Original Message----- From: Bob Stayton [mailto:bobs@sagehill.net] Sent: Wednesday, June 20, 2007 9:27 AM To: Steve Blair; M.Canales.es; docbook-apps@lists.oasis-open.org Subject: Re: [docbook-apps] Whitespace in <indexterm> I checked the FO output under these circumstances, and the destination marker is correctly formed as an empty fo:block or fo:inline, depending on the context, and it has the right id for the indexterm. The index also has a fo:page-citation with the right id reference. So the FO should work. But the error messages during processing indicate that it cannot find the id of the empty marker element, so this is an unresolved cross reference and no page number. If you put any kind of non-blank text inside the empty marker element, the page number appears. So it seems that fop 0.93 doesn't think an empty inline should have an id. I think this is likely a bug. (putting some non-blank text inside the marker is probably not a good idea, as it will introduce formatting artifacts you don't want.) Bob Stayton Sagehill Enterprises DocBook Consulting bobs@sagehill.net ----- Original Message ----- From: "Steve Blair" <sblair@vocera.com> To: "M.Canales.es" <macana@macana-es.com>; <docbook-apps@lists.oasis-open.org> Sent: Wednesday, June 20, 2007 8:22 AM Subject: RE: [docbook-apps] Whitespace in <indexterm> Hi Manuel, > FOP 0.93 creates a PDF file with unwanted whitespace in paragraphs > that use these index entries. >> Copy the match="indexterm" name="indexterm" template found in fo/index.xsl >> to your customization layer. In the name="wrapper.name" variable defined >> here, change >> >> <xsl:when test="$axf.extensions != 0"> >> >> to >> >> <xsl:when test="$axf.extensions != 0 or $fop1.extensions != 0"> This suggestion successfully removes the whitespace, but it also removes the page number from all index entries. This is the best solution, if we can preserve the page numbers. Does anyone know why the page numbers are removed, or how to preserve them? Best, Steve Blair Director of Technical Publications Vocera Communications sblair@vocera.com 408.790.4210 --------------------------------------------------------------------- To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]