cvs commit: xml-fop/src/codegen enumgen.xsl properties.xsl xalan2.filter

[keiron]

keiron  2002/07/25 02:32:26

  Modified:.build.xml
   src/codegen enumgen.xsl properties.xsl
  Removed: src/codegen xalan2.filter
  Log:
  removed unneeded filter
  
  Revision  ChangesPath
  1.56  +2 -11 xml-fop/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/xml-fop/build.xml,v
  retrieving revision 1.55
  retrieving revision 1.56
  diff -u -r1.55 -r1.56
  --- build.xml 1 Jul 2002 11:03:07 -   1.55
  +++ build.xml 25 Jul 2002 09:32:26 -  1.56
  @@ -171,7 +171,7 @@
 
 
 
  -  
  +  
   
   
   
  @@ -215,7 +215,6 @@


   
  - 
   
   
   
  @@ -267,8 +266,6 @@
   
   
  
  -
  -
 
   
 
  @@ -276,15 +273,9 @@
   
   
   
  -
  -
  -  
   
  -  
  -
 
   
  -
 
 
 
  @@ -501,7 +492,7 @@
   
   
  -
  +
   
   
   
  
  
  
  1.5   +1 -1  xml-fop/src/codegen/enumgen.xsl
  
  Index: enumgen.xsl
  ===
  RCS file: /home/cvs/xml-fop/src/codegen/enumgen.xsl,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- enumgen.xsl   4 Mar 2001 21:23:35 -   1.4
  +++ enumgen.xsl   25 Jul 2002 09:32:26 -  1.5
  @@ -32,7 +32,7 @@
  
   
  
  -
  +
   package org.apache.fop.fo.properties;
   
   
  
  
  
  1.16  +1 -1  xml-fop/src/codegen/properties.xsl
  
  Index: properties.xsl
  ===
  RCS file: /home/cvs/xml-fop/src/codegen/properties.xsl,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- properties.xsl23 Feb 2002 16:47:01 -  1.15
  +++ properties.xsl25 Jul 2002 09:32:26 -  1.16
  @@ -204,7 +204,7 @@
  implements 
   
   
  -
  +
   package org.apache.fop.fo.properties;
   
   import java.util.Hashtable;
  
  
  

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

[GUMP] Build Failure - xml-fop

[Sam Ruby]

This email is autogenerated from the output from:



Buildfile: build.xml
Caught exception (org.apache.tools.ant.BuildException) while expanding 
libs-run-classpath: /home/rubys/jakarta/xml-fop/build not found.

init-avail:

init-filters-xalan2:
 [copy] Copying 1 file to /home/rubys/jakarta/xml-fop/build/src/codegen

init:
 [echo] --- Fop 1.0dev [1999-2002] 

prepare:
 [echo] Preparing the build directories
[mkdir] Created dir: 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties
[mkdir] Created dir: 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts
[mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/svg
[mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/conf
[mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/hyph
 [copy] Copying 4 files to /home/rubys/jakarta/xml-fop/build/classes/conf

codegen:
 [echo] Resetting codegen directory
 [copy] Copying 32 files to /home/rubys/jakarta/xml-fop/build/src/codegen
 [echo] Generating the java files from xml resources
[style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/allprops.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/Constants.java
[style] Loading stylesheet 
/home/rubys/jakarta/xml-fop/build/src/codegen/genconst.xsl
[style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml 
to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/fo_ignore_this.java
[style] Loading stylesheet 
/home/rubys/jakarta/xml-fop/build/src/codegen/properties.xsl
[style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml 
to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/FOPropertyMapping.java
[style] Loading stylesheet 
/home/rubys/jakarta/xml-fop/build/src/codegen/propmap.xsl
[style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml 
to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/foenums_ignore_this.java
[style] Loading stylesheet 
/home/rubys/jakarta/xml-fop/build/src/codegen/enumgen.xsl
[style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/encodings.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/CodePointMapping.java
[style] Loading stylesheet 
/home/rubys/jakarta/xml-fop/build/src/codegen/code-point-mapping.xsl
[style] Transforming into 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/CourierBold.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/CourierBold.java
[style] Loading stylesheet 
/home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/Courier.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/Courier.java
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/CourierBoldOblique.xml 
to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/CourierBoldOblique.java
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/CourierOblique.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/CourierOblique.java
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/Helvetica.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/Helvetica.java
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/HelveticaBold.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/HelveticaBold.java
[style] Processing 
/home/rubys/jakarta/xml-fop/src/codegen/HelveticaBoldOblique.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/HelveticaBoldOblique.java
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/HelveticaOblique.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/HelveticaOblique.java
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesBold.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesBold.java
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesBoldItalic.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesBoldItalic.java
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesItalic.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesItalic.java
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesRoman.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesRoman.java
[style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/Sym

Re: AW: AW: AW: Embedding FOP in Servlet

[Oleg Tkachenko]

Martin Ewald wrote:

> your tips were great. It was a classpath problem. After many attempts, I found out 
>that the
> file xerces.jar was missed. I'm so stupid. Now tomcat delivers a pdf-document how I 
>can see
> in my MIE 5. I get the pdf-source-code but I hope I will correct this.
Glad to hear it works, but I should say exception diagnostic is so convolute 
in the case, never could imagine it has something to do with xerces. :)

-- 
Oleg Tkachenko
Multiconn International, Israel


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

OutofMemoryException

[RamanaJV]

Dear group,
I have a big fo file, could be around 100 pages. But the driver
gives me a outofmemoryexception when I give this file to the renderer. I use
AWTRenderer for printing the document. Can't FOP handle big FO documents. Is
there a workaround to get around this memory problem.

Ramana.

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

FO to PCL

[RamanaJV]

Dear group,
Doesn any one have a XSL to convert to FO to PCL. I want to try this
option, since FOP is not able to handle large documents.

Ramana.

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

Re: OutofMemoryException

[Jochen Deubner]

Hi,

it IS capable of rendering large documents. Out of Memory exception ist just
caused by standard JVM Memory assignment of 64M.
Just enlarge the memory for the JVM with parameter -Xmx256m (256m for
256Megs).

Jochen


- Original Message -
From: "RamanaJV" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 25, 2002 12:14 PM
Subject: OutofMemoryException


> Dear group,
> I have a big fo file, could be around 100 pages. But the driver
> gives me a outofmemoryexception when I give this file to the renderer. I
use
> AWTRenderer for printing the document. Can't FOP handle big FO documents.
Is
> there a workaround to get around this memory problem.
>
> Ramana.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>


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

RE: OutofMemoryException

[RamanaJV]

This shows a blue screen, if I terminate the Java program in the middle with
Ctrl-C option. The system showing a fatal error with the Ctrl-C termination.

Ramana.

-Original Message-
From: Jochen Deubner [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 4:19 PM
To: [EMAIL PROTECTED]
Subject: Re: OutofMemoryException


Hi,

it IS capable of rendering large documents. Out of Memory exception ist just
caused by standard JVM Memory assignment of 64M.
Just enlarge the memory for the JVM with parameter -Xmx256m (256m for
256Megs).

Jochen


- Original Message -
From: "RamanaJV" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 25, 2002 12:14 PM
Subject: OutofMemoryException


> Dear group,
> I have a big fo file, could be around 100 pages. But the driver
> gives me a outofmemoryexception when I give this file to the renderer. I
use
> AWTRenderer for printing the document. Can't FOP handle big FO documents.
Is
> there a workaround to get around this memory problem.
>
> Ramana.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>


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

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

RE: OutofMemoryException

[Cyril Rognon]

Ramana,

I guess you can find in the list archive that many of us have encountered 
this memory issue. I have managed to render 50 to 1500 pages documents 
using a machine with 256 Mo RAM . When you want to do that, you have to 
allow your JVM to use a large amount of memory. It can be tricky in windows 
environnement when you want to use more than the max RAM you have. You have 
to let W98 or WinNT or Win2K use some virtual memory. This should not 
trigger any blue screen of death

what is your document made of ? if you have some well known page break, you 
should make a page sequence change there. The memory is happy with short 
page sequences as for this implementation of FOP (meaning 0.20.x).

Again, search for the advice in the archive, it has been said many times : 
short page sequences, jvm memory setting, avoid forward reference when you can.

Good luck

Cyril

At 16:45 25/07/2002 +0530, you wrote:
>This shows a blue screen, if I terminate the Java program in the middle with
>Ctrl-C option. The system showing a fatal error with the Ctrl-C termination.
>
>Ramana.
>
>-Original Message-
>From: Jochen Deubner [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, July 25, 2002 4:19 PM
>To: [EMAIL PROTECTED]
>Subject: Re: OutofMemoryException
>
>
>Hi,
>
>it IS capable of rendering large documents. Out of Memory exception ist just
>caused by standard JVM Memory assignment of 64M.
>Just enlarge the memory for the JVM with parameter -Xmx256m (256m for
>256Megs).


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

RE: OutofMemoryException

[RamanaJV]

Thanx for the response cyril.
I'll try this. How is your new place?

Ramana.

-Original Message-
From: Cyril Rognon [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 5:58 PM
To: [EMAIL PROTECTED]
Subject: RE: OutofMemoryException


Ramana,

I guess you can find in the list archive that many of us have encountered 
this memory issue. I have managed to render 50 to 1500 pages documents 
using a machine with 256 Mo RAM . When you want to do that, you have to 
allow your JVM to use a large amount of memory. It can be tricky in windows 
environnement when you want to use more than the max RAM you have. You have 
to let W98 or WinNT or Win2K use some virtual memory. This should not 
trigger any blue screen of death

what is your document made of ? if you have some well known page break, you 
should make a page sequence change there. The memory is happy with short 
page sequences as for this implementation of FOP (meaning 0.20.x).

Again, search for the advice in the archive, it has been said many times : 
short page sequences, jvm memory setting, avoid forward reference when you
can.

Good luck

Cyril

At 16:45 25/07/2002 +0530, you wrote:
>This shows a blue screen, if I terminate the Java program in the middle
with
>Ctrl-C option. The system showing a fatal error with the Ctrl-C
termination.
>
>Ramana.
>
>-Original Message-
>From: Jochen Deubner [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, July 25, 2002 4:19 PM
>To: [EMAIL PROTECTED]
>Subject: Re: OutofMemoryException
>
>
>Hi,
>
>it IS capable of rendering large documents. Out of Memory exception ist
just
>caused by standard JVM Memory assignment of 64M.
>Just enlarge the memory for the JVM with parameter -Xmx256m (256m for
>256Megs).


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

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

RE: OutofMemoryException

[RamanaJV]

Cyril,
As far your suggestion, I have made the FO to be a small page
sequences (could be around 20 pages per sequence). But, it I'm bugged with
this OutofMemoryException.  My system has 192Mb RAM.  The FO document is
made of tables. There will be two tables per page. There are no forward
references.

Ramana.

-Original Message-
From: Cyril Rognon [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 5:58 PM
To: [EMAIL PROTECTED]
Subject: RE: OutofMemoryException


Ramana,

I guess you can find in the list archive that many of us have encountered 
this memory issue. I have managed to render 50 to 1500 pages documents 
using a machine with 256 Mo RAM . When you want to do that, you have to 
allow your JVM to use a large amount of memory. It can be tricky in windows 
environnement when you want to use more than the max RAM you have. You have 
to let W98 or WinNT or Win2K use some virtual memory. This should not 
trigger any blue screen of death

what is your document made of ? if you have some well known page break, you 
should make a page sequence change there. The memory is happy with short 
page sequences as for this implementation of FOP (meaning 0.20.x).

Again, search for the advice in the archive, it has been said many times : 
short page sequences, jvm memory setting, avoid forward reference when you
can.

Good luck

Cyril

At 16:45 25/07/2002 +0530, you wrote:
>This shows a blue screen, if I terminate the Java program in the middle
with
>Ctrl-C option. The system showing a fatal error with the Ctrl-C
termination.
>
>Ramana.
>
>-Original Message-
>From: Jochen Deubner [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, July 25, 2002 4:19 PM
>To: [EMAIL PROTECTED]
>Subject: Re: OutofMemoryException
>
>
>Hi,
>
>it IS capable of rendering large documents. Out of Memory exception ist
just
>caused by standard JVM Memory assignment of 64M.
>Just enlarge the memory for the JVM with parameter -Xmx256m (256m for
>256Megs).


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

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

RE: OutofMemoryException

[RamanaJV]

Cyril,
As far your suggestion, I have made the FO to be a small page
sequences (could be around 20 pages per sequence). But, it I'm bugged with
this OutofMemoryException.  My system has 192Mb RAM.  The FO document is
made of tables. There will be two tables per page. There are no forward
references.

Ramana.

-Original Message-
From: Cyril Rognon [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 5:58 PM
To: [EMAIL PROTECTED]
Subject: RE: OutofMemoryException


Ramana,

I guess you can find in the list archive that many of us have encountered 
this memory issue. I have managed to render 50 to 1500 pages documents 
using a machine with 256 Mo RAM . When you want to do that, you have to 
allow your JVM to use a large amount of memory. It can be tricky in windows 
environnement when you want to use more than the max RAM you have. You have 
to let W98 or WinNT or Win2K use some virtual memory. This should not 
trigger any blue screen of death

what is your document made of ? if you have some well known page break, you 
should make a page sequence change there. The memory is happy with short 
page sequences as for this implementation of FOP (meaning 0.20.x).

Again, search for the advice in the archive, it has been said many times : 
short page sequences, jvm memory setting, avoid forward reference when you
can.

Good luck

Cyril

At 16:45 25/07/2002 +0530, you wrote:
>This shows a blue screen, if I terminate the Java program in the middle
with
>Ctrl-C option. The system showing a fatal error with the Ctrl-C
termination.
>
>Ramana.
>
>-Original Message-
>From: Jochen Deubner [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, July 25, 2002 4:19 PM
>To: [EMAIL PROTECTED]
>Subject: Re: OutofMemoryException
>
>
>Hi,
>
>it IS capable of rendering large documents. Out of Memory exception ist
just
>caused by standard JVM Memory assignment of 64M.
>Just enlarge the memory for the JVM with parameter -Xmx256m (256m for
>256Megs).


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

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

RE: OutofMemoryException

[Cyril Rognon]

Ramana,

I have a 256 Mo Ram machine that uses JVM -Xms512m -Xmx512m and it runs fine.

I admit that JVM memory settings gives some weird results sometimes. What 
JVM are you using ? I have seen tremendous performance upgrade when we went 
from 1.2 to 1.3. Even better with last 1.4 under Win2K.

Are you sure you have no forward reference ? like some "page x of y" page 
footer ?

Cyril


At 19:00 25/07/2002 +0530, you wrote:

>Cyril,
> As far your suggestion, I have made the FO to be a small page
>sequences (could be around 20 pages per sequence). But, it I'm bugged with
>this OutofMemoryException.  My system has 192Mb RAM.  The FO document is
>made of tables. There will be two tables per page. There are no forward
>references.
>
>Ramana.


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

Page count & first-rest-last

[miguel_sas]

Hi fop-developers-users,

I'm new to FOP and I've started with a document that needs different
footers for the first, rest and last page. Unfortunatly, as reported in the
bug database, fop do not apply the page-master for the last page, only
first and rest work properly.

Any work-arround?

Second, I'd like to know the total number of pages, to print 'page n of N'
Have you any trick for this?

Thanks in advance.

Miquel Sas


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

RE: OutofMemoryException

[RamanaJV]

Cyril,
I'm sure that I don't have any forward references and page footers.
What I have in the page sequence is a static text , some blocks followed by
a table.  The JDK i use is 1.4. What could be the problem and can u suggest
a solution..

Ramana.

-Original Message-
From: Cyril Rognon [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 7:29 PM
To: [EMAIL PROTECTED]
Subject: RE: OutofMemoryException


Ramana,

I have a 256 Mo Ram machine that uses JVM -Xms512m -Xmx512m and it runs
fine.

I admit that JVM memory settings gives some weird results sometimes. What 
JVM are you using ? I have seen tremendous performance upgrade when we went 
from 1.2 to 1.3. Even better with last 1.4 under Win2K.

Are you sure you have no forward reference ? like some "page x of y" page 
footer ?

Cyril


At 19:00 25/07/2002 +0530, you wrote:

>Cyril,
> As far your suggestion, I have made the FO to be a small page
>sequences (could be around 20 pages per sequence). But, it I'm bugged with
>this OutofMemoryException.  My system has 192Mb RAM.  The FO document is
>made of tables. There will be two tables per page. There are no forward
>references.
>
>Ramana.


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

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

RE: OutofMemoryException

[Louis . Masters]

Ramana:
Is it dumping out FOP error messages even though the report seems to be
working?  I think these errors can be related to overflows within your
context areas which I have seen posted as causing increased memory
consumption.
-Lou





RamanaJV <[EMAIL PROTECTED]> on 07/25/2002 10:42:32

Please respond to [EMAIL PROTECTED]

To:   [EMAIL PROTECTED]
cc:

Subject:  RE: OutofMemoryException


Cyril,
   I'm sure that I don't have any forward references and page
footers.
What I have in the page sequence is a static text , some blocks followed by
a table.  The JDK i use is 1.4. What could be the problem and can u suggest
a solution..

Ramana.

-Original Message-
From: Cyril Rognon [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 7:29 PM
To: [EMAIL PROTECTED]
Subject: RE: OutofMemoryException


Ramana,

I have a 256 Mo Ram machine that uses JVM -Xms512m -Xmx512m and it runs
fine.

I admit that JVM memory settings gives some weird results sometimes. What
JVM are you using ? I have seen tremendous performance upgrade when we went

from 1.2 to 1.3. Even better with last 1.4 under Win2K.

Are you sure you have no forward reference ? like some "page x of y" page
footer ?

Cyril


At 19:00 25/07/2002 +0530, you wrote:

>Cyril,
> As far your suggestion, I have made the FO to be a small page
>sequences (could be around 20 pages per sequence). But, it I'm bugged with
>this OutofMemoryException.  My system has 192Mb RAM.  The FO document is
>made of tables. There will be two tables per page. There are no forward
>references.
>
>Ramana.


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

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









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

RE: OutofMemoryException

[RamanaJV]

No Louis,
It is saying java.lang.OutOfMemoryError in the Driver.render(...)
statement.  If, I print some pages below than 70, it is fine. But, if I try
more than 70, the OutOfMemoryError. 

Ramana.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 8:23 PM
To: [EMAIL PROTECTED]
Subject: RE: OutofMemoryException



Ramana:
Is it dumping out FOP error messages even though the report seems to be
working?  I think these errors can be related to overflows within your
context areas which I have seen posted as causing increased memory
consumption.
-Lou





RamanaJV <[EMAIL PROTECTED]> on 07/25/2002 10:42:32

Please respond to [EMAIL PROTECTED]

To:   [EMAIL PROTECTED]
cc:

Subject:  RE: OutofMemoryException


Cyril,
   I'm sure that I don't have any forward references and page
footers.
What I have in the page sequence is a static text , some blocks followed by
a table.  The JDK i use is 1.4. What could be the problem and can u suggest
a solution..

Ramana.

-Original Message-
From: Cyril Rognon [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 7:29 PM
To: [EMAIL PROTECTED]
Subject: RE: OutofMemoryException


Ramana,

I have a 256 Mo Ram machine that uses JVM -Xms512m -Xmx512m and it runs
fine.

I admit that JVM memory settings gives some weird results sometimes. What
JVM are you using ? I have seen tremendous performance upgrade when we went

from 1.2 to 1.3. Even better with last 1.4 under Win2K.

Are you sure you have no forward reference ? like some "page x of y" page
footer ?

Cyril


At 19:00 25/07/2002 +0530, you wrote:

>Cyril,
> As far your suggestion, I have made the FO to be a small page
>sequences (could be around 20 pages per sequence). But, it I'm bugged with
>this OutofMemoryException.  My system has 192Mb RAM.  The FO document is
>made of tables. There will be two tables per page. There are no forward
>references.
>
>Ramana.


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

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









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

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

RE: OutofMemoryException

[Cyril Rognon]

Lou is right.

could you tell us what FOP outputs when you use the debug mode ? (-d option 
in command line).

Cyril

At 10:53 25/07/2002 -0400, you wrote:

>Ramana:
>Is it dumping out FOP error messages even though the report seems to be
>working?  I think these errors can be related to overflows within your
>context areas which I have seen posted as causing increased memory
>consumption.
>-Lou


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

AW: OutofMemoryException

[J.U. Anderegg]

To attack the problem:

o split the job into 2 steps:
- XSL transformation writes XSL:FO to a file
- FOP formats the file

o use another renderer: text e.g.

o vary the input
- reduce the volume: when does it blow up?
- eliminate distinct elements

You will pretty soon see the source of the troubles.  


Hansuli Anderegg



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

OutofMemoryException

[RamanaJV]

 I have generated the XSL:FO into a file.   I have used the FOP -d option
and pasted the debug messages thus got in the attached file "temp".  I can
even send the FO file individually to test the load, since the mail to the
mailing test bounces with that attachment.

After these error messages, finally the saying in my DOS prompt.

 Exception in thread "main" java.lang.OutOfMemoryError

I have also set the Driver for PCLRenderer, but the same problem.




test
Description: Binary data

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

RE: OutofMemoryException

[Cyril Rognon]

I have had some similar problem with one document : Some hyphenated text in 
a cell that was on two rows (row span) : FOP warned me about some "I cannot 
hyphenate!". I have not seen this with small documents (bellow 500 pages) 
but with large ones FOP went on an infinite loop. I did exactly like 
Hansuli Anderegg is telling you : tried to noarrow the problem by lowering 
the FO size and hard testing the troubleshooting part.

I know it is not some "magic" method that will help you to solve your 
problem in twelve seconds but this is the best we have.

You have to try with debug on.

Good luck.

Cyril

At 20:22 25/07/2002 +0530, you wrote:
>No Louis,
> It is saying java.lang.OutOfMemoryError in the Driver.render(...)
>statement.  If, I print some pages below than 70, it is fine. But, if I try
>more than 70, the OutOfMemoryError.
>
>Ramana.


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

RE: OutofMemoryException

[RamanaJV]

Yep ,
I have narrowed in on the problem somewhat. Followed Hansuli
Anderegg and found that the problem is with AWTRenderer itself, with PDF and
TXT, no OutOfMemory. 
Now, I request the group to tell me whether there are any PDF
viewers, that I can use in my JavaApplication to show the thus generated
output.
   Please, help me

Ramana.

-Original Message-
From: Cyril Rognon [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 8:53 PM
To: [EMAIL PROTECTED]
Subject: RE: OutofMemoryException


I have had some similar problem with one document : Some hyphenated text in 
a cell that was on two rows (row span) : FOP warned me about some "I cannot 
hyphenate!". I have not seen this with small documents (bellow 500 pages) 
but with large ones FOP went on an infinite loop. I did exactly like 
Hansuli Anderegg is telling you : tried to noarrow the problem by lowering 
the FO size and hard testing the troubleshooting part.

I know it is not some "magic" method that will help you to solve your 
problem in twelve seconds but this is the best we have.

You have to try with debug on.

Good luck.

Cyril

At 20:22 25/07/2002 +0530, you wrote:
>No Louis,
> It is saying java.lang.OutOfMemoryError in the Driver.render(...)
>statement.  If, I print some pages below than 70, it is fine. But, if I try
>more than 70, the OutOfMemoryError.
>
>Ramana.


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

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

RE: OutofMemoryException

[Arnd Beißner]

> Now, I request the group to tell me whether there are any PDF
> viewers, that I can use in my JavaApplication to show the thus generated
> output.

There is a PDF bean on the Adobe web site that I used successfully some 
time
ago. I think it supports PDF features including PDF 1.1.

Hope this helps,

Arnd Beissner
--
Cappelino Informationstechnologie GmbH
Arnd Beißner
Bahnhofstr. 3, 71063 Sindelfingen, Germany
Email: [EMAIL PROTECTED]
Phone: +49-7031-463458
Fax: +49-7031-463460
Mobile: +49-173-3016917


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

[PDF Viewer] Utility request

[RamanaJV]

Dear FOP developers,
After seeing the OutOfMemoryError, the AWT renderer is causing, why
don't thinking of providing a PDF viewer in the FOP itself. I think, this
will be useful so much. I don't think people couldn't have ever thought
about it, but is it diffucult to do so?
   I feel, FOP is very much useful with the PDF viewer. What do
others say?

Ramana.

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

RE: [PDF Viewer] Utility request

[Rhett Aultman]

I see FOP's role as being a data transformer first and foremost.  We may want to 
consider packaging a PDF viewer with FOP, but I'd recommend against putting it *IN* 
FOP.

-Original Message-
From: RamanaJV [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 12:47 PM
To: [EMAIL PROTECTED]
Subject: [PDF Viewer] Utility request


Dear FOP developers,
After seeing the OutOfMemoryError, the AWT renderer is causing, why
don't thinking of providing a PDF viewer in the FOP itself. I think, this
will be useful so much. I don't think people couldn't have ever thought
about it, but is it diffucult to do so?
   I feel, FOP is very much useful with the PDF viewer. What do
others say?

Ramana.

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


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

Re: OutofMemoryException

[Oleg Tkachenko]

RamanaJV wrote:
>   I have narrowed in on the problem somewhat. Followed Hansuli
> Anderegg and found that the problem is with AWTRenderer itself, with PDF and
> TXT, no OutOfMemory. 
Hmm, probably loading swing classes finally exhausts available memory.

-- 
Oleg Tkachenko
Multiconn International, Israel


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

RE: [PDF Viewer] Utility request

[Victor Mote]

Ramana wrote:

> ... why don't thinking of providing a PDF viewer in the FOP itself.

Perhaps I am missing something. Is the freely available Acrobat Reader
insufficient for the task?

Victor Mote (mailto:[EMAIL PROTECTED])
Enterprise Outfitters (www.outfitr.com)
2025 Eddington Way
Colorado Springs, Colorado 80916
Voice 719-622-0650, Fax 720-293-0044


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

Re: [PDF Viewer] Utility request

[Ralph LaChance]

At 12:46 PM 7/25/02, you wrote:
> After seeing the OutOfMemoryError, the AWT renderer is causing, why
>don't thinking of providing a PDF viewer in the FOP itself. I think, this
>will be useful so much. I don't think people couldn't have ever thought
>about it, but is it diffucult to do so?
>I feel, FOP is very much useful with the PDF viewer. What do
>others say?

Seems to me it might be a lot simpler to fix the awt viewer...

Also, oddly enough doing a viewer against pdf is rather tricky -
Adobe put an un-supported java-bean on their web site, but it
is buggy and hasn't been updated in 2 or so years. The only
commercial pkg (a toolset; some assembly required) I know
of probably would pose a licensing challenge (understatement)



 ' Best,
 -Ralph LaChance



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

Re: EOFException while creating metrics for the font file

[J.Pietschmann]

Sachio Yagi wrote:
>>Reading /usr/lib/X11/fonts/TrueType/japanese.st/typefaces/hgrgb98.ttf...
>>
>>java.io.EOFException: Reached EOF, file size=65536 offset=7092058
...
> Can anybody please guide me how to solve this problem or  how to Use
> Japanese
> font in HP-UX.

The TTF reader wants to read the number of glyphs in
the file and follows a pointer in the Font file header,
which doesn't point to a valid file offset.
You'll have to track down why the TTFReader thinks there
should be something else in the TTF file. There could
be a bug in the TTFReader, or you have a malformed font
file.
This problem shows up regularly with far-east fon files,
unfortunately, any font I could get works. You could do
a great service to the public by tracking down why your
font cannot be read and posst the results to the list.

J.Pietschmann


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

Re: Page count & first-rest-last

[J.Pietschmann]

[EMAIL PROTECTED] wrote:
> I'm new to FOP and I've started with a document that needs different
> footers for the first, rest and last page. Unfortunatly, as reported in the
> bug database, fop do not apply the page-master for the last page, only
> first and rest work properly.

It depends on what is different on the last page from
the rest.
Another possibility is a two pass approach:
Define the following page master:
   
  
  
  
   

Get the page count and insert pageCount-2 for the 1000.
If you generate the FO with XSLT You can automate this with
a small Java wrapper, take
  http://marc.theaimsgroup.com/?l=fop-user&m=102002702026609&w=2
and replace the "page-count" XSLT parameter with an appropriately
used "maximum-repeats" parameter.

> Second, I'd like to know the total number of pages, to print 'page n of N'
> Have you any trick for this?

FAQ. See
  http://marc.theaimsgroup.com/?l=fop-user&m=102052610605212&w=2

J.Pietschmann


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

Black images

[Darrel Riekhof]

Some images, when FOP embeds them in the PDF, show up as all black rectangles.  The 
size of the image is correct.  However, this only occurs if you are using 16 bit color 
or higher.  If you lower the color res down to 256 colors, then images always show up 
in the pdf in acrobat reader.  Client is Win2000, Acrobat Reader 5, Fop server process 
is running on red hat linux 7.2 server, fop 2.0.3.

I think this behavior only started happening in FOP 2.0.3, but I'm not totally sure 
about this.  I can't figure out if it is an acrobat or fop thing.  Is this a known 
issue with FOP?  Anyone found a work-around for this?

Darrel

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

CTM - e (tx) and f (ty) divided by 1000

[Kevin O'Neill]

I've been having a look at org.apache.fop.area.CTM and I notice that the
toArray() method modifies the e and f elements of the matrix by dividing
them by 1000 before returning them in the array. This seems to be there
to support one function
org.apache.fop.render.pdf.PDFRenderer.startVParea() where it is used to
create an AffineTransform for the current state.

As I'm using the CTM class to generate PDF files outside of xslf:fo and
I don't want e and f to be divided by 1000.

My quick solution was to add a method toPDFArray() that does what the
current toArray() does and update toArray() not to do the division and
updated the call in startVParea().

I think a better solution would be to create a helper class in
org.apache.fop.render.pdf that does the toPDF functions and remove the
knowledge of the pdf rendering requirements from org.apache.fop.area.CTM
If this seems like to right way to go I'll create some patches for this.


-k


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