Re: [xsl] XSL-FO: Forcing blocks with images to start from the next page instead of clipping the image?

Subject: Re: [xsl] XSL-FO: Forcing blocks with images to start from the next page instead of clipping the image?
From: Joel Peltonen <joel.peltonen@xxxxxxxxx>
Date: Thu, 24 May 2012 09:32:08 +0300
Interestingly, the images flow to the next page if I remove the span="all"
attribute from my blocks. It must somehow interfere with page breaks.

I can move on for now by simply removing the spans="all", and hoping
I won't run into problems where I would really need it.

On 23 May 2012 17:29, G. Ken Holman <gkholman@xxxxxxxxxxxxxxxxxxxx> wrote:
> At 2012-05-23 17:26 +0300, Joel Peltonen wrote:
>>
>> Greetings!
>>
>> I'm converting an XSL-FO file into pdf with Altsoft Xml2PDF 1.2.2.
>>
>> When I have images that start near the end of a page they are clipped so
>> that
>> the portion that does not fit on a page is not visible.
>
>
> That sounds like a bug to me.  I would have expected a page-break to
> accommodate the image.
>> I can get the images to
>> start correctly from the next page if I remove the block entirely, but
>> then I'm
>> missing some attributes.
>>
>> With markup like this the image gets clipped:
>> <fo:block text-align="right" span="all" margin-bottom="3pt">
>>    <fo:external-graphic content-height="scale-to-fit"
>>                content-width="100mm" src="url(C:/someimage.jpg)" />
>> </fo:block>
>>
>> Simply <fo:external-graphic ... />  without the block works and the image
>> starts from the next page, but I'm afraid I will lose my alignment, span
>> and
>> margin! Any advice?
>
>
> Have you tried adding a keep constraint to the block?
>
>   keep-together.within-column="always"

I have tried it, but it had no effect at all if span="all" was present,
neither did .within-page="always" nor ="1".

Many thanks for your input!

 - Joel

Current Thread