display-align

[Kaiser Christian (SV SC RS T33)]

Hi,

is it possible that FOP ignores the 'disply-align' attribute of
'external-graphic' ?
If yes: Is it planned to implement it?
My solution to center images is to make a  wrapper
around it. 

Thank's for any response,
Chris

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

Re: how FOP uses fonts

[Keiron Liddle]

On Fri, 28 Sep 2001 15:54:58 adel ben wrote:
> Hi all,
> 
> I am working On adding arbic fonts to FOP. Do anyone know how FOP uses
> fonts? should I alter or add some classes? or just configure FOP? 
> any help will be welcome.
> with regards,
> adel

This page should tell you what you need to know to setup other fonts.
http://xml.apache.org/fop/fonts.html

Note that fop currently only handles lr-tb writing mode.

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

Re: fop problem

[Rob Heittman]

why do you conclude this is a FOP error?  This looks like Cocoon is 
having a problem with basic transformations.  Did the problem suddenly 
begin when you installed FOP?

- Rob


eric.deandrea wrote:

>I am running cocoon 1.8 with fop 0.20.1 and when I try and load a page into
>the browser I get the following error. Can anyone help me?
>
>Publishing Engine could not be initialized.
>   java.lang.RuntimeException: Factory error:  unknown exception
>creating " org.apache.cocoon.transformer.XalanTransformer" :
>java.lang.VerifyError: (class:
>org/apache/cocoon/transformer/XalanTransformer, method: transform signature:
>(Lorg/w3c/dom/Document;Ljava/lang/String;Lorg/w3c/dom/Document;Ljava/lang/St
>ring;Lorg/w3c/dom/Document;Ljava/util/Dictionary;)Lorg/w3c/dom/Document;)
>Incompatible object 
>   at java.lang.Throwable.fillInStackTrace(Native Method)
>   at java.lang.Throwable.fillInStackTrace(Compiled Code)
>   at java.lang.Throwable.(Compiled Code)
>   at java.lang.Exception.(Compiled Code)
>   at java.lang.RuntimeException.(RuntimeException.java:47)
>   at
>org.apache.cocoon.framework.Manager.create(Manager.java:116)
>   at org.apache.cocoon.Engine.(Engine.java:144)
>   at org.apache.cocoon.Engine.getInstance(Engine.java:218)
>   at org.apache.cocoon.Cocoon.init(Cocoon.java:141)
>   at
>com.netscape.server.http.servlet.NSServletEntity.load(NSServletEntity.java:3
>77)
>   at
>com.netscape.server.http.servlet.NSServletEntity.update(NSServletEntity.java
>:149)
>   at
>com.netscape.server.http.servlet.NSServletRunner.Service(NSServletRunner.jav
>a:469)
>
>
>-Eric
>
>
>Eric Deandrea
>Software Engineer  (978) 698-6351  
>Inforonics, Inc.   [EMAIL PROTECTED]
>30 Porter Rd.
>Littleton, MA 01460
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, email: [EMAIL PROTECTED]
>





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

DO NOT REPLY [Bug 3898] New: - fails if id is in block with break-before="page"

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3898

 fails if id is in block with break-before="page"

   Summary:  fails if id is in block with
break-before="page"
   Product: Fop
   Version: 0.17
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Normal
  Priority: Other
 Component: general
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Version: FOP 0.20

If you put the id attribute on a block which has attribute break-before="page", 
the page-number-citation doesn't work. Example:
Introduction: Page 
Introduction

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

[GUMP] Build Failure - Fop

[Sam Ruby]

This email is autogenerated from the output from:



Buildfile: build.xml

init-avail:

init-filters-xalan1:

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

init:
 [echo] --- Fop 0.20.1 [1999-2001] 

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 3 files to /home/rubys/jakarta/xml-fop/build/classes/conf

codegen:
 [echo] Resetting codegen directory
 [copy] Copying 35 files to /home/rubys/jakarta/xml-fop/build/src/codegen
 [echo] Generating the java files from xml resources
 [xslt] 
 [xslt] xslt 
 [xslt] in: ./build/src/codegen/allprops.xml
 [xslt] style: ./build/src/codegen/genconst.xsl
 [xslt] out: ./build/src/org/apache/fop/fo/properties/Constants.java
 [xslt] 
 [xslt] 
 [xslt] xslt 
 [xslt] in: ./build/src/codegen/foproperties.xml
 [xslt] style: ./build/src/codegen/properties.xsl
 [xslt] out: ./build/src/org/apache/fop/fo/properties/fo_ignore_this.java
 [xslt] 
 [xslt] 
 [xslt] xslt 
 [xslt] in: ./build/src/codegen/foproperties.xml
 [xslt] style: ./build/src/codegen/propmap.xsl
 [xslt] out: ./build/src/org/apache/fop/fo/properties/FOPropertyMapping.java
 [xslt] 
 [xslt] 
 [xslt] xslt 
 [xslt] in: ./build/src/codegen/foproperties.xml
 [xslt] style: ./build/src/codegen/enumgen.xsl
 [xslt] out: ./build/src/org/apache/fop/fo/properties/foenums_ignore_this.java
 [xslt] 
 [xslt] 
 [xslt] xslt 
 [xslt] in: ./build/src/codegen/extproperties.xml
 [xslt] style: ./build/src/codegen/properties.xsl
 [xslt] out: ./build/src/org/apache/fop/fo/properties/ext_ignore_this.java
 [xslt] 
 [xslt] 
 [xslt] xslt 
 [xslt] in: ./build/src/codegen/extproperties.xml
 [xslt] style: ./build/src/codegen/propmap.xsl
 [xslt] out: ./build/src/org/apache/fop/fo/properties/ExtensionPropertyMapping.java
 [xslt] 
 [xslt] 
 [xslt] xslt 
 [xslt] in: ./build/src/codegen/extproperties.xml
 [xslt] style: ./build/src/codegen/enumgen.xsl
 [xslt] out: ./build/src/org/apache/fop/fo/properties/extenums_ignore_this.java
 [xslt] 
 [xslt] 
 [xslt] xslt 
 [xslt] in: ./build/src/codegen/charlist.xml
 [xslt] style: ./build/src/codegen/code-point-mapping.xsl
 [xslt] out: ./build/src/org/apache/fop/render/pdf/CodePointMapping.java
 [xslt] 
 [xslt] 
 [xslt] xslt 
 [xslt] in: ./build/src/codegen/Courier.xml
 [xslt] style: ./build/src/codegen/font-file.xsl
 [xslt] out: ./build/src/org/apache/fop/render/pdf/fonts/Courier.java
 [xslt] 
 [xslt] 
 [xslt] xslt 
 [xslt] in: ./build/src/codegen/Courier-Oblique.xml
 [xslt] style: ./build/src/codegen/font-file.xsl
 [xslt] out: ./build/src/org/apache/fop/render/pdf/fonts/CourierOblique.java
 [xslt] 
 [xslt] 
 [xslt] xslt 
 [xslt] in: ./build/src/codegen/Courier-Bold.xml
 [xslt] style: ./build/src/codegen/font-file.xsl
 [xslt] out: ./build/src/org/apache/fop/render/pdf/fonts/CourierBold.java
 [xslt] 
 [xslt] 
 [xslt] xslt 
 [xslt] in: ./build/src/codegen/Courier-BoldOblique.xml
 [xslt] style: ./build/src/codegen/font-file.xsl
 [xslt] out: ./build/src/org/apache/fop/render/pdf/fonts/CourierBoldOblique.java
 [xslt] 
 [xslt] 
 [xslt] xslt 
 [xslt] in: ./build/src/codegen/Helvetica.xml
 [xslt] style: ./build/src/codegen/font-file.xsl
 [xslt] out: ./build/src/org/apache/fop/render/pdf/fonts/Helvetica.java
 [xslt] 
 [xslt] 
 [xslt] xslt 
 [xslt] in: ./build/src/codegen/Hel

Re: Performance

[Arved Sandstrom]

At 06:08 PM 10/1/01 +0900, you wrote:
>As Keiron said that performance increased with just using HashMap 
>instead of Hashtable. How about using ArrayList instead of Vector? Well, 
>it depends on how much Vector is used in FOP.
>Another thought is the way the FO tree and area trees are implemented. 
>There will be probably some changes with the redesign. However, the 
>approach taken by Xalan may also be useful in FOP. In Xalan 2, the DOM 
>has been replaced by DTM (Document Table Model) which uses tables of 
>integers to represent the document, reducing all comparisons (of node 
>names, etc.) to integer comparisons. Of course, Xalan benefits mostly 
>with the faster XPath axis iterators of this implementation which are 
>not relevant to FOP. Nevetherless, if not performance, DTM or the 
>appropiate for FOP offers a lot of savings on memory usage.
>Just a few thoughts, it may trigger some ideas.
>
>Carlos

Hi, Carlos

Hopefully the high-level design will identify the set of questions that we 
must pose to the FO "tree" and "area tree" structures (I quote those terms 
to indicate that they are conceptual trees, and an implementation can do 
whatever it likes). At the moment we really do not have a good handle on 
exactly what those questions are - we can all think of some of them, but we 
have no master comprehensive list that can then inform detailed design and 
implementation.

I agree with you...it's a good idea to be aware of what "sister" projects 
are doing in terms of data structures.

Regards,
Arved

Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia


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

Performance

[Carlos Villegas]

As Keiron said that performance increased with just using HashMap 
instead of Hashtable. How about using ArrayList instead of Vector? Well, 
it depends on how much Vector is used in FOP.
Another thought is the way the FO tree and area trees are implemented. 
There will be probably some changes with the redesign. However, the 
approach taken by Xalan may also be useful in FOP. In Xalan 2, the DOM 
has been replaced by DTM (Document Table Model) which uses tables of 
integers to represent the document, reducing all comparisons (of node 
names, etc.) to integer comparisons. Of course, Xalan benefits mostly 
with the faster XPath axis iterators of this implementation which are 
not relevant to FOP. Nevetherless, if not performance, DTM or the 
appropiate for FOP offers a lot of savings on memory usage.
Just a few thoughts, it may trigger some ideas.

Carlos


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