Hi Jeremias:
Also, when I put the following as the header
FOP complains with the following :
SEVERE: javax.xml.transform.TransformerException: Border and padding for
region "Header" must be '0' (See 6.4.13 in XSL 1.0).
javax.xml.transform.TransformerException:
org.apache.fop.fo.expr.Property
Thanks, Chris.
Is there any workaround to solve the problem? One solution could be to
distribute the border-width parameters in adjacent cells, where adjacency is
with column margin or row margin? Any other workaround?
Regards,
Debasish
-Original Message-
From: Chris Bowditch [mailto:[E
Many thanks, Jeremias. If we don't use block-container, how can we supply
the padding parameters? Can we supply that in the region too?
Regards,
Debasish
-Original Message-
From: Jeremias Maerki [mailto:[EMAIL PROTECTED]
Sent: Friday, August 18, 2006 1:58 AM
To: fop-users@xmlgraphics.ap
Interisting reading ;) thanx for the pointers...
So far, i can setup java to handle 1.4gb ram for heap... (using the -Xms and
-Xmx parameters)... more gives an error when creating the JVM...
Will try the -XX:+AggressiveHeap -XX:+UseLargePages tomorow... or so...
Anyway, i can assure everyone th
On Aug 17, 2006, at 22:34, Jeremias Maerki wrote:
Hi,
Uh, sorry, I somehow missed your hint about "not thread safe". I
thought
it was something simpler. Your additional details seem to confirm that
it's about thread-safety.
Seems like the real clue is this:
3, if I close the open-window q
Not sure what to do here. Sorry. Looks like some side-effects from our
line-breaking algorithm.
On 16.08.2006 17:10:05 Buckman Ekow wrote:
> > Hello,
> >
> > I'm working with FOP 0.92 and trying to use fo:leader.
> > I've got problem when i'm using two fo:leader in one fo:block.
> >
> > FOP gene
Uh, sorry, I somehow missed your hint about "not thread safe". I thought
it was something simpler. Your additional details seem to confirm that
it's about thread-safety. Could you get the whole stack trace for us?
The problem is that the part you showed is not the right one. There's a
nested except
Two problems:
- You don't specify the extent property for Header and LeftSide.
- You use fixed positioned block-containers which actually makes FOP
ignore the whole region setup, because fixed positions block-containers
are absolutely positioned relatively to the upper left corner of the
page. So,
Hi,
Sorry I cant put my code here, it involves 10+ java code, and a 400+ lines
xslt, plus lots .jar files.
I hope I can get some hint for this problem. Debug probably will not help me
since this is not happen always, debug means process code slowly and that
probably will not generate a err then.
FOP uses Jakarta Commons Logging as logging abstraction. Please consult
its documentation to redirect all log output to a different target.
http://xmlgraphics.apache.org/fop/0.92/embedding.html#basic-logging
http://jakarta.apache.org/commons/logging/
I generally use -Djava.util.logging.config.fil
Somehow, your setup seems to swallow the actual error message:
Error(32/50): fo:external-graphic is not a valid child element of fo:table-cell.
Can't tell from here what's going wrong on your side.
On 17.08.2006 11:13:42 Fabian Zeindl wrote:
> Andreas L Delmelle schrieb:
> >> Sorry, I forgot that
Yeah, you can either buy hardware, get a different JVM or use different
settings (see below), or you try to figure out a way to split those
large page-sequences you have. I'd go for the latter. The ultimate
option would be to help us make FOP better to actually be able to
process such big page-sequ
There's no way we can assist you without an actual FO that causes this
exception. So, you'll have to produce an FO file from one of your
documents you know causes the error and you'll have to try to anonymize
the FO file without losing the ability to reproduce the exception if the
content is proble
On Aug 17, 2006, at 15:25, Henric Rosvall wrote:
Hi,
Currently the PDFTrancoder in Batik only has support for creating a
single page in the PDF, even though FOP has support for creating
multiple pages. I want to modify the PDFTranscoder in Batik 1.6 to
enable it to recieve multiple areas o
Title: Message
Hi
!
Currently the
PDFTrancoder in Batik only has support for creating a single page in the PDF,
even though FOP has support for creating multiple pages. I want
to modify the PDFTranscoder in Batik 1.6 to enable it to recieve
multiple areas of interest, and then rendering e
Debasish Jana wrote:
Quick question:
Does FOP 0.92 support border-collapse="collapse" for fo:table?
I need to collapse adjacent cell borders to one
Quick Answer: No, sorry!
Chris
-
To unsubscribe, e-mail: [EMAIL PROTECTE
Quick question:
Does FOP 0.92 support border-collapse="collapse" for fo:table?
I need to collapse adjacent cell borders to one
Regards,
Debasish
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMA
Hi:
I am facing a problem with margin and padding.
The associated xsl-fo file is enclosed below.
I have a section (simple-page-master) that has margins on all four sides as
10.0pt. The section's start (flow name = LeftSide) has left-padding as 10.0
pt and top-padding as 10.0 pt. The start part h
I know this may look like a noob question... (it is for me at least)...
I fail to see how to config fop to log to a file instead of to the standard
output (which isn't that much standard because isn't pipeable to a file
[seams to be log to console instead of stdout]).
Can someone help pls?
(if
Andreas L Delmelle schrieb:
>> Sorry, I forgot that. I already figured out the error. Fop 0.20
>> displayed the wrong xml statements. Fop 0.92 didn't display anything.
>
> Hmm... The only time I remember running into this, was as a consequence
> of the settings of the default JDK logger. (logging.
20 matches
Mail list logo
