RE: DOCBOOK-APPS: Re: xsl-fo driver problems

[David Cramer <dcramer@broadjump.com>]

For what it's worth, XEP was doing the exact same thing and they
interpreted it as a bug in XEP. I think they've probably fixed it by
now, but have never bothered to test the xsls without the workaround
they suggested: adding keep-together.within-column attrs to the outer
block in addition to the keep-with-next:

"if a text chunk is embraced into more than one fo:block elements,
'keep-with-next.within-column' works only if specified on the innermost 
block - unless there is a 'keep-together.within-column' on the same
or upper block that contains 'keep-with-next.within-column'."

Perhaps the same thing would work with PassiveTeX. If so, it's easy to
add to formal.title.properties.

David

> -----Original Message-----
> From: Norman Walsh [mailto:ndw@nwalsh.com]
> Sent: Tuesday, May 07, 2002 9:46 PM
> To: Dennis Grace
> Cc: docbook-apps@lists.oasis-open.org
> Subject: DOCBOOK-APPS: Re: xsl-fo driver problems
> 
> 
> / Dennis Grace <dgrace@us.ibm.com> was heard to say:
> | Anyway, Norm, I'm using XSLTPROC and PassiveTeX. I found my 
> problem, but
> | I'm still not sure whether it's a PassiveTeX or an XSL 
> problem. I described
> | the whole shebang here:
> | 
> http://lists.oasis-open.org/archives/docbook-apps/200204/msg00281.html
> 
> Ok, the short answer is, I think putting the keep on the inner block
> is perfectly fine so that's what I've done. I'm not sure if the FO
> spec is clear on whether or not PassiveTeX is "doing the right thing."
> 
> I'm inclined to think not, but I'll investigate a little further.
> 
>                                         Be seeing you,
>                                           norm