Thanks, I've have thought of upgrading to 0.91beta, but I'm a bit hesitant. I 
found the problem with my table though, I got a corrupt character in the coding 
somehow.

A little off the subject though, but can you please help me with a new problem? 
I can't load umlauts into my xsl from an xml sheet, im thinking that I must use 
a special characters or something for characters like é, ë, ï, ect. If you 
could help me please, id appreciate it a lot.

Thanks,


-----Original Message-----
From: Chris Bowditch [mailto:[EMAIL PROTECTED] 
Sent: 20 March 2006 12:00 PM
To: [email protected]
Subject: Re: Keep-together.

Andre Groeneveld wrote:

> Hi All,
> 
>  
> 
> Can some-one please help me, I have a table with two rows, then I've got 
> a table in each of these rows, the reason why I did it this way, is to 
> keep the two rows together using "keep-together.within-page="always", 
> but when I got to work today, they told me that the documents are wrong, 
> and when I looked, I saw that the first row's table is overflowing to 
> the next page instead of the table flowing over to the next page.

You don't say what version of FOP you are using which is key if we are 
going to be able to help you *sigh* I guess you must be using 0.20.5 as 
you seem to be using the table-row workaround which is a 0.20.5 thing.

> 
> I tried to see whether some-one maybe changed the template, but I 
> couldn't see any changes. Can some-one please tell me how I should use 
> the keep, so that the data wont overflow onto the next page?

It could be that your inner table that is being broken across a page is 
longer than a page. Otherwise I have no idea, 0.20.5 was quite buggy, 
especially with regard to keeps. My recommendation would be to upgrade 
to 0.91beta, where keeps are implemented on tables, so you won't need to 
wrap them, in an outer table.

Chris



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Confidentiality Caution and Disclaimer

This message and/or any attachment thereto ("the message")
contains privileged and confidential information intended
only for the recipient named above. 
If you are not the intended recipient of this message,
please erase it permanently once you have notified the
sender, per return e-mail, that you have received the
message in error.
Unless the sender is duly authorised by either the Telesure
Group, or any of its subsidiary companies or I.S Services
("the Group") to send this message and unless the content
of this message is also duly authorised by the Group, any
views expressed in this message are those of the individual
sender and the Group will not accept liability therefore,
nor for any consequential damage arising therefrom.
Any recipient of an unacceptable communication, a chain
letter or offensive material of any nature is requested
to report it to [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to