[xep-support] Strange phenomenon in Table of Contents

[Kees de Grauw]

Hi Cristian and Volodymyr,

Volodymyr wrote: 
> Try to remove keep-with-next.within-line rule from <fo:basic-link/>.

I can reproduce Cristian's behaviour even without all keep-with-next
attributes. Even removing the complete <fo:inline> elements and all other
non-essential attributes does not help (see modified code below).

<fo:block text-align-last="justify">
    <fo:basic-link internal-destination="id411140">2.4.4. Echo Request
message to a destination IP address 255.255.25111</fo:basic-link>
    <fo:leader leader-pattern="dots" /><fo:basic-link
internal-destination="id411140"><fo:page-number-citation
ref-id="id411140"/></fo:basic-link>
</fo:block>

Apparently there is some critical length.

Kees

-----Original Message-----
From: owner-xep-support at renderx.com
[mailto:owner-xep-support at renderx.com]On Behalf Of Ettinger, Christian
Sent: Monday, 18 September 2006 11:33
To: xep-support at renderx.com
Subject: [xep-support] Strange phenomenon in Table of Contents


Hi,
 
I discovered a strange phenomenon in my Table of Contents when creating the
PDF file with XEP.
I use the Docbook stylesheets to generate the FO file, and these stylesheets
produce the following FO code:
 
<fo:block xmlns:axf="http://www.antennahouse.com/names/XSL/Extensions"
text-align-last="justify" text-align="start" color="blue" end-indent="24pt"
last-line-end-indent="-24pt">
  <fo:inline keep-with-next.within-line="always">
    <fo:basic-link internal-destination="id411140">2.4.4. Echo Request
message to a destination IP address of
255.255.255.255</fo:basic-link>
  </fo:inline>
  <fo:inline keep-together.within-line="always"> <fo:leader
leader-pattern="dots" leader-pattern-width="3pt"
leader-alignment="reference-area" keep-with-next.within-line="always"/>
<fo:basic-link internal-destination="id411140"><fo:page-number-citation
ref-id="id411140"/></fo:basic-link></fo:inline>
</fo:block>

So far, this is correct, but look at the attached file what XEP does with
it.
There seems to be some critical line length, where XEP just breaks the page
number but does not extend the leader into the next line.

Does anybody have an idea how I can overcome this problem? Or any ideas on
the source of this phenomenon?

Thanks in advance,
Christian
 
--
Dipl.-Ing. (FH) Christian Ettinger, Business Unit PD-36
3SOFT GmbH - Member of the Elektrobit Group,
Frauenweiherstraße 14, 91058 Erlangen, Germany
Phone: +49 (9131) 7701-249  mailto:christian.ettinger at 3SOFT.de
Fax: +49 (9131) 7701-333  http://www.3SOFT.de <http://www.3soft.de/> 
 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 2888 bytes
Desc: not available
URL: <http://lists.renderx.com/pipermail/xep-support/attachments/20060918/1e0fb26b/attachment.bin>