LineArea patch

[stephanie <cr...@goldinc.com>]

I had to make the following changes in order to get Fop to compile.  I
believe that this was introduced when "src/codegen properties.xml"x was
modified.

Fotis, I'd like to see anything which get me back into processing xml
data into pdf's.  If XalanCommandLine does this (and I don't really care
how slow it is) I'd like to see it go into 0.14.

By the way, I had an old svg.jar in ...../lib/ext which had been causing
me problems (I've never been comfortable with classpath things).
Thanks for the help Fotis
Stephanie


Index: LineArea.java
===================================================================
RCS file:
/home/cvspublic/xml-fop/src/org/apache/fop/layout/LineArea.java,v
retrieving revision 1.16
diff -r1.16 LineArea.java
436c436
<  case TextAlign.CENTERED: // center
---
>  case TextAlign.CENTER: // center
441c441
<  case TextAlign.JUSTIFIED: // justify
---
>  case TextAlign.JUSTIFY: // justify

Re: LineArea patch

[Fotis Jannidis <fo...@lrz.uni-muenchen.de>]

> I had to make the following changes in order to get Fop to compile.  I
> believe that this was introduced when "src/codegen properties.xml"x was
> modified.
Thanks. I fixed this.
 
> Fotis, I'd like to see anything which get me back into processing xml
> data into pdf's.  If XalanCommandLine does this (and I don't really care
> how slow it is) I'd like to see it go into 0.14.
The problem is not speed, but memory. For a 2 MB xml file using the xml2pdf stylesheet 
in /docs/xml-docs I had to increase the max memory for the JVM to 128MB. Fop is a 
memory hog anyway because it holds fo tree and area tree completely in memory, but 
XalanCommandLie adds the complete fo file to it. 

I committed it anyway and hope it helps.

Fotis