Glen Mazza wrote:
FOP's goals should be (1) to be compliant/accurate with the spec
The Area Tree is an implementation specification: either the XSL editors
remove it from the specs or they specify it precisely as a portable,
device-independent print file format. I ran Chuck Paussa's FO schema
Peter B. West wrote:
While I don't denigrate any of these ongoing efforts, I am increasingly
of the view that everything occurring between the reading of the fo xml
and the layout of the area tree is interconnected in very nasty and
intricate ways. The description of this process in the Rec
Chris Bowditch wrote:
What you say is true, but I think you missed one thing from your
analysis:
what if solution A took x seconds and B took x+2 seconds, but B had a
greater level of compliance and produced better results than solution A?
Then you would want to give the users the choice
Response below (one of these glorious days, I can stop using Outlook...)
-Original Message-
From: Glen Mazza [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 27, 2003 7:49 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: hack to avoid memory overflow with tables
FOP is ultimately
--- Rhett Aultman [EMAIL PROTECTED] wrote:
Moreover, is FOP really that far from, say, the HTML
rendering engine in a web browser with respect to
layout decisions? I see a lot of interpretations
and opinions going on in those engines, which is
why two browsers sometimes interpret my HTML
J.Pietschmann schrieb:
Hi all,
now that there are a few more modifications in the maintenance
branch, waht about including the fixes mentione here:
http://marc.theaimsgroup.com/?l=fop-userm=105371539508744w=2
It would need some testing (read 0.20.5rc4)
Nooo, no more RCs for 0.20.5 please
It's
My thoughts tend to go in the direction to factor out support subsystems
like fonts, PDF, SVG etc. These are areas where a lot of improvements
have happened during the last months and I'm currently ending up
applying bugfixes in two places. As Peter I see a lot of complications
in trying to bring
From: Glen Mazza [EMAIL PROTECTED]
snip/
1.) Generate multiple document types accurately.
2.) Generate a high number of very large documents in
a very short amount of time, with high, very
large, and very short taken to their mathematical
limits.
While there can be plenty of discussion of how
--- Chris Bowditch [EMAIL PROTECTED] wrote:
From: Glen Mazza [EMAIL PROTECTED]
snip/
1.) Generate multiple document types accurately.
2.) Generate a high number of very large documents
in
a very short amount of time, with high, very
large, and very short taken to their
From: Glen Mazza [EMAIL PROTECTED]
snip/
As for producing better results (after
compliance)--I would like to think the system designed
could be such that the renderers are user-pluggable
and -extensible--but my current knowledge of FOP is
not formed enough to comment intelligently on that.
Back
Jeremias Maerki wrote:
I'm slowly getting the impression it may be better if we really totally
modularize FOP (splitting it up into several independently usable
subprojects) so development is only split in the layout field which is
the major problem-child here. But that alone would take long
--- Victor Mote [EMAIL PROTECTED] wrote:
The goal would be
to eventually drop the
maintenance branch layout system into the redesign
code as an implementation
of LayoutStrategy. It will always be a deficient
implementation, but right
now it is the best one that we have (else we would
be
Victor, Jeremias,
Just a couple of notes on the discussion below.
It is a mistake to say, because there is no great ferment of coding,
that nothing is being done on the redesign of layout. I, for one, am
currently giving the layout a great deal of thought, triggered in my
case by the
[EMAIL PROTECTED] wrote:
The markers work fine
except in one instance: if ROW4 and ROW5 overflow into the next page, the
retrieve marker will pull ROW5MARKERDATA1 and ignore ROW4MARKERDATA1 even
though ROW 4 is a distinctly new row. If more than two rows overflow, it
seems to work OK (i.e
respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: table overflow and markers on 20.2
[EMAIL PROTECTED] wrote:
The markers work fine
except in one instance: if ROW4 and ROW5 overflow into the next page,
the
retrieve marker will pull ROW5MARKERDATA1 and ignore
/show_bug.cgi?id=7323
Content overflow in fo:table-cell if content too long
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
/show_bug.cgi?id=7323
Content overflow in fo:table-cell if content too long
[EMAIL PROTECTED] changed:
What|Removed |Added
OS/Version|Windows NT/2K |All
/show_bug.cgi?id=7323
Content overflow in fo:table-cell if content too long
Summary: Content overflow in fo:table-cell if content too long
Product: Fop
Version: 0.20.3
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity
Folks:
Is overflow=hidden supported on a block? I'm trying to get my block data
to truncate at the cell boundary.
TIA,
-Lou
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Title: table-cells and clipping (overflow=hidden)
Hello,
I've got a problem with tables and clipping.
In my document, content of a table cell shouldn't exceed the tabel cell.
For this reason I tried to use the clip or overflow property, but it doesn't work.
Content containing spaces
Hi Folks!
I wanted to put a logo on a letter using a block-container
where I put my image in. The image should be clipped if it is
too big.
But all that happens is that the image disapears. Also if I
used overflow=visible the image disapears. Is that a bug or
a feature??
Christian
Fop doesn't support block-container. See:
http://xml.apache.org/fop/implemented.html
Regards, Etwin
- Original Message -
From: Beer, Christian [EMAIL PROTECTED]
To: Fop-liste (E-Mail) [EMAIL PROTECTED]
Sent: Tuesday, October 23, 2001 4:09 PM
Subject: overflow=hidden and big images
That page must be out of date. I use block-container is several places
successfully.
Scott
-Original Message-
From: Etwin van Krimpen [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 23, 2001 10:40 AM
To: [EMAIL PROTECTED]
Subject: Re: overflow=hidden and big images...
Fop doesn't
Actually, it does, although not completely.
jw
-Original Message-
From: Etwin van Krimpen [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 23, 2001 9:40 AM
To: [EMAIL PROTECTED]
Subject: Re: overflow=hidden and big images...
Fop doesn't support block-container. See:
http
Hi*,
how can I get an overflow=hidden or something similar in a fo:table-row?
I'm using the old Version 0.16.
Thanks,
Karin Thaens
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
=0mm left=0mm overflow=hidden
fo:block font-size={$Font-Size} font-family={$Font-Family}
font-weight={$Font-Weight} font-style={$Font-Style}
color={$Font-Color} overflow=hidden
!-- Space for the signature-line... --
fo:block space
Hi all,
I'd like to specify a particular page-master (regions) for the first page and another
page-master (other regions) for rest of the doc wich is the overflow of the first page.
How could I do so ?
Other question :
Is it possible to avoid the page break into a block ?
(page-break-inside
I am looking for help with overflow-paginate function of XSL. I have data
elements that overflow the block sizes and overflow-paginate=8.00in
doesn't seem to be workning for me.
Robyn MacDuff
[EMAIL PROTECTED]
-
To unsubscribe
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2170
*** shadow/2170 Wed Jun 13 21:56:55 2001
--- shadow/2170.tmp.18535 Mon Jun 18 01:39:14 2001
***
*** 2,9
| Table Column overflow - endless loop
29 matches
Mail list logo
