-Original Message-
From: Susanta Dash [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 14, 2006 6:54 AM
I appreciate your honest replies.
This is for Pascal:
As a workaround, you can try to play with fo:block-container in
absolute position, but you have to cut the
Susanta Dash wrote:
Hey guys, I can't wait for XSL-FO 1.1 and can't see any alternative. Can you
guys just guide me to accomplish my need; I'm trying to get the exact point
where to break the text, so that I can just move the rest of the text to the
next column. I'm thinking to use AWT renderer
Hey guys,
Are we on the same page yet? OR Am I making any mistake to understand how to layout this problem OR this feature ismissing entirely or in the build I'm using(0.20.5)?
Thanks.
On 9/13/06, Susanta Dash [EMAIL PROTECTED] wrote:
Glen,Actually i've a paragraph(s) of text, ABC was just an
Susanta, I think you're a victim of your earlier thread-hijacking,
check this post:
http://marc.theaimsgroup.com/?l=fop-userm=115812992904817w=2
Basically, I believe the reason why you are using tables is because XSL
1.0 does not provided the advanced layout functionality you want with
I appreciate your honest replies.
This is for Pascal:
As a workaround, you can try to play with fo:block-container in absolute
position, but you have to cut the flow-text yourself.
When you say cut the flow-text yourself, do you mean that I've to figure
out the column breaks and explicitly
Susanta Dash wrote:
Here is the problem I'm facing while rendering it in FOP.
I've two rows, first one has 3 columns and the next has 2 columns. The
text within these rows need to be flowed to the next column.
Why wouldn't having one column for each row and letting the text flow
normally
Glen,
Actually i've a paragraph(s) of text, ABC was just an example. Like in my
previous example i had 2 paragraphs and to be fit in 2 different rows each.
It's not at all a problem if i have same number of columns in each row, but
variable column count is an issue.
Thanks.
-Original
