Footnote space is indeed deducted twice. This seems to be a long
standing bug, none of the commits since 18 months shows any interesting
change in the area.
I'll think about a fix tomorrow.
J.Pietschmann
-
To unsubscribe, e-mail:
Giampiero Longobardi wrote:
With FOP release 0.20.5rc3a and the following xsl-fo code, the PDF result
contains too much blank space between main-reference and footnote-reference
area in page 1 and I don't understand why.
The "4. A decorrere dal 1° gennaio è incrementata, a favore dei soggetti
"
Chris,
the result is the same even if I delete the following declaration from the
fo:page-sequence:
Giampiero
- Original Message -
From: "Chris Bowditch" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, June 16, 2003 1:32 PM
Subject: Re: Space between main-reference and fo
Thanks Mike.
Peter
Mike Ferrando wrote:
Peter W.,
I was speaking of the recent past, this year. The errors I was aware
of have been corrected. Here is my e-mail answered by Victor
concerning these errors.(below)
--
Peter B. West http://www.powerup.com.au/~pbwest/resume.html
---
I agree with you. I am not at all an AWT/Swing expert. When I was
investigating this it turned out to be surprisingly difficult to get
reliable information about threadsafty of these classes. Especially when I
tried to find out where exactly the problem is inside AWT/Swing and what
could be done t
Reto wrote:
> I have investigated this and have done some multithreaded tests with
> AWTRenderer a few months ago. The conclusions can be found in the archives
> of this list.
> Summary:
> - AWTRenderer and all subclasses of it (TIFFRenderer...) are NOT
> threadsave.
> - It is not threadsave becau
I don't understand the problem.
AFAIK 'content-width'/'content-height' isn't imlemented but 'width'/'height'
isn't required to show an image!
FOP tries to render the image in its original size except it overflows your
imageable area.
In this case the image will be scaled down to fit at least one w
In mathematical perspective this may be the solution
Let X be the total number of pages [ In this case it is 8 ]
Let Y be the current page.
Then the display on each page will be : Y / [(X/2)+1]
Assuming that (X/2) returns an integer.
-Original Message-
From: Leonard Wolters [mailto:[EM
Peter W.,
I was speaking of the recent past, this year. The errors I was aware
of have been corrected. Here is my e-mail answered by Victor
concerning these errors.(below)
Mike F.
===
Date: Thu, 1 May 2003 11:12:17 -0700 (PDT)
From: "Mike Ferrando" <[EMAIL PROTECTED]>
hello i am facing a problem for a long time and asked for help from forum 2 times but unfortunately i didnt get the solution yet. pls help me...in my case i want to show some images in a row. but i dont want to fix the sizes of the images, i meanthe images will be shown at their original size.
hello i am facing a problem for a long time and asked for help from forum 2 times but unfortunately i didnt get the solution yet. pls help me...in my case i want to show some images in a row. but i dont want to fix the sizes of the images, i meanthe images will be shown at their original size.
PrintRenderer uses the Result of AWTRenderer...
see: http://xml.apache.org/fop/output.html#general
citation start<<
General Information
Fonts
Most FOP renderers use a FOP-specific system for font registration. However,
the AWT and print renderers use the java awt package, which gets its font
i
From: "Giampiero Longobardi" <[EMAIL PROTECTED]>
With FOP release 0.20.5rc3a and the following xsl-fo code, the PDF result
contains too much blank space between main-reference and footnote-reference
area in page 1 and I don't understand why.
I believe that primitive support for footnote-separator w
Hello,
I am using FOP v0.20.4 (and I have also tried 0.20.5rc3a) to generate both
a PDF file for archival perposes and also to print directly to a printer.
The resulting PDF file is formatted exectly as I expect, however, the
printed output differs in a couple of areas. The printed copy is a littl
I have investigated this and have done some multithreaded tests with
AWTRenderer a few months ago. The conclusions can be found in the archives
of this list.
Summary:
- AWTRenderer and all subclasses of it (TIFFRenderer...) are NOT
threadsave.
- It is not threadsave because the underlaying AWT lib
15 matches
Mail list logo
