Alt-Design: Preliminary results FO tree build test
Fop-devs, Herewith the preliminary results of running the alt.design FO tree build against the 51 page test document supplied by Bertrand. Thanks for the file Bertrand. The file yields a tree of 11044 nodes. The pull buffer is set to 64, the maximum size of the FoXMLEvent pool is 74, and the total number of FoXMLEvent objects created is 78 (next event id -1). The sytem is a 256Mb PII laptop running Sun's Java 1.4.1 under Redhat 7.3. Elapsed time from the beginning of org.apache.fop.apps.Fop main to the end of the FO tree build is 15960. The preorder scan of the tree takes that to 16176. The test is run within a 'time' command with the results 18.02s real11.71s user 0.24s system Memory figures after a final GC, besides being somewhat confusing, are Total memory after GC : 16334848 Free memory after GC: 7242184 The command was: time java $Fop -fo /home/pbw/public_html/xml/real-life-51-page-document.fo The full output from the test run follows. userConfigFileName reading user configuration file userconfig.xml Can't find user configuration file userconfig.xml in user locations base directory: file:/home/pbw/public_html/xml/ Version: FOP 0.20.0 Alt-Design Input mode: fo fo input file: /home/pbw/public_html/xml/real-life-51-page-document.fo Output mode: pdf output file: /usr/local/src/xml-fop_20_Alt/docs/examples/tests/test.pdf OPTIONS user configuration file: userconfig.xml debug mode on don't dump configuration [default] low level areas generated[default] quiet mode off [default] FOP Developers Build using SAX parser org.apache.xerces.parsers.SAXParser Starting parserThread parserThread started foThread started simple-page-master ok simple-page-master ok simple-page-master ok Making sparsePropsSet for static-content. Making sparsePropsSet for flow. Making sparsePropsSet for static-content. Making sparsePropsSet for static-content. Making sparsePropsSet for flow. Size of event pool: 74 Next event id : 78 Back from buildFoTree Elapsed time: 15960 # of FONodes: 11044 Back from driver.run() Elapsed time: 16176 Total memory before run : 2031616 Total memory after run : 11886592 Total memory after GC : 16334848 Diff before/after total : 9854976 Diff before/GC total: 14303232 Diff after/GC total : 4448256 Free memory before run : 1670696 Free memory after run : 2114040 Free memory after GC: 7242184 Diff before/after free : 443344 Diff before/GC free : 5571488 Diff after/GC free : 5128144 cg() freed : 5128144 18.02s real11.71s user 0.24s system Peter -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: cvs commit: xml-fop/src/documentation/content/xdocs/design/alt.design classes-overview.xml
You may have seen my CVS commit yesterday evening. I changed my name in the author tag of fonts.xml. It now contains the proper UTF-8 encoding of an a-umlaut (ä). I had no error messages from Forrest and the HTML result looked correct. - person name=Jeremias Maerki email=/ + person name=Jeremias Märki email=/ Thinking about it, the ü when literally embedded in a UTF-8 encoded document should throw an error IMO. If I think about the implications of having to use character references for text written in chinese, for example On 02.12.2002 15:57:48 Keiron Liddle wrote: On Mon, 2002-12-02 at 15:49, Jeremias Maerki wrote: Keiron, is that really necessary? If proper UTF-8 encoding would be used (as declared implicitly), these cryptic character references would not be necessary, right? I kept getting errors with validation and conversion with cocoon. The error message where usually something like: unkown error. I don't know what is causing the problem. At least this works with forrest now. A normal character would be preferrable if the problems can be solved. On 02.12.2002 15:34:04 keiron wrote: -über-class to accommodate everything that applies to +#xFC;ber-class to accommodate everything that applies to Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: cvscommit: xml-fop/src/documentation/content/xdocs/design/alt.designclasses-overview.xml
On Mon, 2002-12-02 at 22:19, Peter B. West wrote: Keiron, I will be updating this documentation in the next few days, and I will fix the encoding at the same time, unless there is a more urgent need. Could you leave the character as it is for the moment, just in case there is still some problem. By all means update the document encoding. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/resources/schema catalog
keiron 2002/12/03 02:04:02 Added: src/documentation/resources/schema catalog Log: compliance catalog entry Revision ChangesPath 1.1 xml-fop/src/documentation/resources/schema/catalog Index: catalog === -- OASIS TR 9401 Catalog for Forrest -- OVERRIDE YES -- custom doctype -- PUBLIC -//APACHE//DTD Compliance V1.0//EN dtd/compliance-v10.dtd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation README
keiron 2002/12/03 02:06:10 Added: src/documentation README Log: readme for generating docs Revision ChangesPath 1.1 xml-fop/src/documentation/README Index: README === To update the docs: The documentation is generated using forrest (http://xml.apache.org/forrest/). The current procedure is: - checkout xml-forrest module - run: build.sh(bat) dist - follow instructions to set FORREST_HOME and path - go to xml-fop directory - run forrest(.bat) The documents will then be placed in build/site/ NOTE: the compliance.html currently does not work, it can be fixed by adding the dtd ref to: build/tmp/context/resources/schema/catalog and placing the dtd in: build/tmp/context/resources/schema/dtd/ To update website - put the generated docs into the xml-site module targets/fop/ this could be done by simlinking the destination to the targets/fop - commit the documents - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using Apache FOP to create multiple-page PDFs usingPDFDocumentGraphics2D
jcplerm wrote: Actually, I managed to find a solution late last night that apparently works. It should be further refined by the FOP team, of course. I am sending attached two files: Could you please save it in bugzilla as enhancement? Otherwise it's going to be lost. PS. Don't forget to start bugzilla entry summary with [PATCH]. -- Oleg Tkachenko eXperanto team Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: website
On Mon, 2002-12-02 at 21:37, Victor Mote wrote: I see that Keiron has republished the web site. Here are some comments: 1. Keiron, would it help any, now that you have gotten the basic flow going, for one of us to take the web-site publication burden from you? I know Christian is involved in doc. If he does not wish to do it, I would be happy to run that. If reasonable, I would make an effort to publish it daily. What steps are required? Should we put the steps in a document (which would be visible from the web)? I realize that long-term Forrest does this automatically. I have just committed a readme with the current steps. As things progress this will change. As this is likely to change at the moment maybe we could leave it for a bit before putting on a webpage. It could be a good idea to bring together some of the procedures on a webpage, such as making a release, updating docs etc. 2. The new Compliance document is now visible at http://xml.apache.org/fop/compliance.html. It refers to color-coding which, by passing through Forrest, we don't have yet. I'll work on either removing the color-coding reference or getting the color-coding to work. colour coding would good I think, maybe you could make a dtd enhancement suggestion. 3. I envision the Compliance document to be a replacement for the Implemented and Limitations documents. It was built from information on those two pages, as well as a complete listing of objects properties, and the information about standard compliance levels. Is there any objection to removing these documents? I'll double-check to make sure no useful information falls through the cracks. 4. The information in Compliance is probably not complete or accurate. I'm going to be culling through the mailing lists to try to get some of it cleaned up. If you see something that is not right, please either 1) fix it, 2) submit a patch, or 3) send me an email I'll fix it. Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop forrest.properties
keiron 2002/12/03 02:53:48
Modified:.forrest.properties
Log:
aØ°AæÍ9 ܼ¹ÂNÀ4dÂÐ)£
Revision ChangesPath
1.4 +5 -1 xml-fop/forrest.properties
Index: forrest.properties
===
RCS file: /home/cvs/xml-fop/forrest.properties,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- forrest.properties30 Nov 2002 08:54:25 - 1.3
+++ forrest.properties3 Dec 2002 10:53:48 - 1.4
@@ -25,5 +25,9 @@
#project.lib-dir=${project.content-dir}/lib
#project.classes-dir=${project.content-dir}/classes
-forrest.validate.xdocs.excludes=compliance.xml
+forrest.validate=true
+forrest.validate.xdocs=${forrest.validate}
+forrest.validate.skinconf=${forrest.validate}
+
+forrest.validate.failonerror=true
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: xml-fop forrest.properties
That is supposed to say: all docs now validate
Something went wrong...
On Tue, 2002-12-03 at 11:53, [EMAIL PROTECTED] wrote:
keiron 2002/12/03 02:53:48
Modified:.forrest.properties
Log:
aذAæ͘9 ܼ¹ÂNÀ4dÂÐ)£
Revision ChangesPath
1.4 +5 -1 xml-fop/forrest.properties
Index: forrest.properties
===
RCS file: /home/cvs/xml-fop/forrest.properties,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- forrest.properties 30 Nov 2002 08:54:25 - 1.3
+++ forrest.properties 3 Dec 2002 10:53:48 - 1.4
@@ -25,5 +25,9 @@
#project.lib-dir=${project.content-dir}/lib
#project.classes-dir=${project.content-dir}/classes
-forrest.validate.xdocs.excludes=compliance.xml
+forrest.validate=true
+forrest.validate.xdocs=${forrest.validate}
+forrest.validate.skinconf=${forrest.validate}
+
+forrest.validate.failonerror=true
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation forrest.diff
keiron 2002/12/03 03:00:23
Modified:src/documentation forrest.diff
Log:
updated to latest forrest
Revision ChangesPath
1.4 +71 -43xml-fop/src/documentation/forrest.diff
Index: forrest.diff
===
RCS file: /home/cvs/xml-fop/src/documentation/forrest.diff,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- forrest.diff 19 Nov 2002 07:32:14 - 1.3
+++ forrest.diff 3 Dec 2002 11:00:23 - 1.4
@@ -1,10 +1,55 @@
+Index: src/resources/skins/common/xslt/fo/pdfoutline.xsl
+===
+RCS file:
/home/cvspublic/xml-forrest/src/resources/skins/common/xslt/fo/pdfoutline.xsl,v
+retrieving revision 1.1
+diff -u -r1.1 pdfoutline.xsl
+--- src/resources/skins/common/xslt/fo/pdfoutline.xsl3 Dec 2002 00:23:19
- 1.1
src/resources/skins/common/xslt/fo/pdfoutline.xsl3 Dec 2002 10:57:33
-
+@@ -1,26 +1,22 @@
+ ?xml version=1.0 encoding=UTF-8?
+-!DOCTYPE xsl:stylesheet [
+-!ENTITY copy #169;
+-!ENTITY nbsp #160;
+-!ENTITY degr #186;
+-!ENTITY sup2 #178;
+-!ENTITY sup3 #179;]
+-xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:fo=http://www.w3.org/1999/XSL/Format;
xmlns:fox=http://xml.apache.org/fop/extensions;
xmlns:documentation=http://sealcorp.com.au/documentation;
++xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:fo=http://www.w3.org/1999/XSL/Format;
xmlns:fox=http://xml.apache.org/fop/extensions;
+
+ xsl:template match=document mode=outline
+- fox:outline internal-destination={generate-id()}
+-fox:label
+- xsl:value-of select=header/title/
+- xsl:text - /xsl:text
+- xsl:value-of select=header/authors/person/@name/
+-/fox:label
+-xsl:apply-templates select=body/section mode=outline/
+- /fox:outline
++ fox:bookmarks
++fox:outline internal-destination={generate-id()}
++ fox:label
++xsl:value-of select=header/title/
++ /fox:label
++ xsl:apply-templates select=body/section mode=outline/
++/fox:outline
++ /fox:bookmarks
+ /xsl:template
+
+ xsl:template match=section mode=outline
+ fox:outline internal-destination={generate-id()}
+ fox:label
++ xsl:number format=1.1.1.1.1.1.1 count=section level=multiple/
++ xsl:text /xsl:text
+ xsl:value-of select=title/
+ /fox:label
+ xsl:apply-templates select=section mode=outline/
Index: src/resources/skins/common/xslt/fo/document2fo.xsl
===
RCS file:
/home/cvspublic/xml-forrest/src/resources/skins/common/xslt/fo/document2fo.xsl,v
-retrieving revision 1.2
-diff -u -r1.2 document2fo.xsl
src/resources/skins/common/xslt/fo/document2fo.xsl 16 Nov 2002 22:58:50
- 1.2
-+++ src/resources/skins/common/xslt/fo/document2fo.xsl 19 Nov 2002 07:30:58
-
+retrieving revision 1.3
+diff -u -r1.3 document2fo.xsl
+--- src/resources/skins/common/xslt/fo/document2fo.xsl 3 Dec 2002 00:23:19
- 1.3
src/resources/skins/common/xslt/fo/document2fo.xsl 3 Dec 2002 10:57:33
-
@@ -2,6 +2,7 @@
xsl:stylesheet xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
@@ -13,16 +58,12 @@
version=1.0
xsl:output method=xml/
-@@ -80,14 +81,57 @@
- /fo:repeatable-page-master-alternatives
- /fo:page-sequence-master
+@@ -84,14 +85,34 @@
/fo:layout-master-set
+
+ xsl:apply-templates select=/document mode=outline/
-
+
-+ fox:bookmarks
-+xsl:apply-templates select=document/body/section mode=bookmarks/
-+ /fox:bookmarks
-+
fo:page-sequence master-reference=book
+fo:titlexsl:value-of select=document/header/title//fo:title
xsl:apply-templates/
@@ -32,25 +73,6 @@
/xsl:template
-
+
-+ xsl:template match=section mode=bookmarks
-+fox:outline internal-destination={generate-id()}
-+ fox:label
-+xsl:number format=1.1.1.1.1.1.1 count=section level=multiple/
-+xsl:text /xsl:text
-+xsl:value-of select=title/
-+ /fox:label
-+ xsl:apply-templates mode=bookmarks/
-+/fox:outline
-+ /xsl:template
-+
-+ xsl:template match=* mode=bookmarks
-+xsl:apply-templates mode=bookmarks/
-+ /xsl:template
-+
-+ xsl:template match=text() mode=bookmarks
-+!-- suppress text nodes in bookmarks --
-+ /xsl:template
-+
+ xsl:template name=info
+fo:block-container font-style=italic absolute-position=absolute
+ left=0pt top=0pt right=6.25in bottom=150pt
@@ -73,7 +95,7 @@
xsl:template match=document
DO NOT REPLY [Bug 15020] New: - Reuse of fo-tree
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15020. 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=15020 Reuse of fo-tree Summary: Reuse of fo-tree Product: Fop Version: 1.0dev Platform: Other URL: http://nagoya.apache.org/eyebrowse/ReadMsg?listName=fop- [EMAIL PROTECTED]msgNo=4462 OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: general AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Requested by Henrik Olsson [EMAIL PROTECTED], see http://nagoya.apache.org/eyebrowse/ReadMsg?[EMAIL PROTECTED]msgNo=4462. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 15022] New: - PATCH resubmit
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15022. 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=15022 PATCH resubmit Summary: PATCH resubmit Product: Fop Version: all Platform: All URL: http://www.rootshell.be/~hornyakl/download/patches/fop/p dfinfo.diff OS/Version: All Status: NEW Severity: Normal Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hi *! Oleg asked me to resubmit this patch, so here it is. see url... The grammar error was fixed. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: website
Keiron Liddle wrote: On Mon, 2002-12-02 at 21:37, Victor Mote wrote: [...] 2. The new Compliance document is now visible at http://xml.apache.org/fop/compliance.html. It refers to color-coding which, by passing through Forrest, we don't have yet. I'll work on either removing the color-coding reference or getting the color-coding to work. colour coding would good I think, maybe you could make a dtd enhancement suggestion. Color coding is easily possible with chaperon, that is part of Cocoon and also Forrest (for our ongoing wiki-like editing development). Send us a RFE about it with suggestions on the DTD changes and it'll help the process, thanks :-) -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 15022] - PATCH resubmit
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15022. 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=15022 PATCH resubmit [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2002-12-03 17:00 --- *** This bug has been marked as a duplicate of 1 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 14444] - [PATCH] a performance patch for PDFInfo class
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1. 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=1 [PATCH] a performance patch for PDFInfo class --- Additional Comments From [EMAIL PROTECTED] 2002-12-03 17:00 --- *** Bug 15022 has been marked as a duplicate of this bug. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Alt-Design: Preliminary results FO tree build test
Peter B. West wrote: Herewith the preliminary results of running the alt.design FO tree build against the 51 page test document supplied by Bertrand. What is included in this measurement? I presume it's fo parsing, userconfig processing and fo tree buiding? Thanks for the file Bertrand. The file yields a tree of 11044 nodes. The pull buffer is set to 64, the maximum size of the FoXMLEvent pool is 74, and the total number of FoXMLEvent objects created is 78 (next event id -1). The sytem is a 256Mb PII laptop running Sun's Java 1.4.1 under Redhat 7.3. Elapsed time from the beginning of org.apache.fop.apps.Fop main to the end of the FO tree build is 15960. The preorder scan of the tree takes that to 16176. The test is run within a 'time' command with the results 18.02s real11.71s user 0.24s system It's rather interesting to compare it with the trunk code. But I believe we need real profiler software results to make any serious conclusions. -- Oleg Tkachenko eXperanto team Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Alt-Design: Preliminary results FO tree build test
Hmmm...maybe we could use a JVM profiler like jProf (http://starship.python.net/crew/garyp/jProf.html) for this? -Original Message- From: Oleg Tkachenko [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 03, 2002 12:11 PM To: [EMAIL PROTECTED] Subject: Re: Alt-Design: Preliminary results FO tree build test Peter B. West wrote: Herewith the preliminary results of running the alt.design FO tree build against the 51 page test document supplied by Bertrand. What is included in this measurement? I presume it's fo parsing, userconfig processing and fo tree buiding? Thanks for the file Bertrand. The file yields a tree of 11044 nodes. The pull buffer is set to 64, the maximum size of the FoXMLEvent pool is 74, and the total number of FoXMLEvent objects created is 78 (next event id -1). The sytem is a 256Mb PII laptop running Sun's Java 1.4.1 under Redhat 7.3. Elapsed time from the beginning of org.apache.fop.apps.Fop main to the end of the FO tree build is 15960. The preorder scan of the tree takes that to 16176. The test is run within a 'time' command with the results 18.02s real11.71s user 0.24s system It's rather interesting to compare it with the trunk code. But I believe we need real profiler software results to make any serious conclusions. -- Oleg Tkachenko eXperanto team Multiconn Technologies, Israel - 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 14248] - 51-page FO example, could be added to the samples
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14248. 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=14248 51-page FO example, could be added to the samples --- Additional Comments From [EMAIL PROTECTED] 2002-12-03 20:50 --- FOPImageFactory has a comment regarding URI syntax near the beginning of the Make method. Formally, sect. 5.11 should be authoritative indeed. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Getting breaks: revisited
Oleg Tkachenko wrote: btw, how does such a case addressed by the spec? Apparently FOP, antenna and xep do squeeze content. Isn't it an example of overconstrained geometry (5.3.4)? It can be interpreted as such in the presented case. Use height instead of width and a table whose rows are kept together instead of a block to make it more interesting (from the users point of view, for the processor it may still be an example of overconstrained geometry, but this becomes far fetched rapidly). J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP Servlet, contrib stuff and tutorial
Keiron Liddle wrote: - move contrib/servlet to examples/servlet - move contrib/plan to examples/plan - move contrib/mathml to examples/mathml One of the purposes that these serve is to demonstrate how to write an extension and for FOP to pick it up in the classpath. This might take away that. Granted for plan and mathml, but the servlet sees real use, and getting it built easily may be in order. In either case I personally expect source which can be of real use in the src tree rather than anywhere else, and I don't think it matters much if the written documentation points to examples/something or src/java/org/something/else, as long as it is distributed with the binary distro, and this shouldn't be too hard to arrange. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
alt.design info
Hi all, I would like to know about fop alt.design. Where can i find the documentation for this? will it change the entire old design ro part of it? What should i do to involve in alt.design. Thanks in advance. Thanks Sri __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 15048] New: - Unwanted page break after image linked by external-graphic in region body
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15048. 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=15048 Unwanted page break after image linked by external-graphic in region body Summary: Unwanted page break after image linked by external- graphic in region body Product: Fop Version: 0.20.3 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I want to generate a pdf with a list of images. I suppose them to be shown in the pdf one by one. And, if the two images are size small enough, they can be placed in 1 page together. However, I find that no matter how small the images are, there must be a page break for each image. The sample code is like this: : fo:block page-break-before=avoid page-break-after=avoid xsl:for-each select=ADVICE/IMAGE fo:wrapper fo:external-graphic xsl:attribute name=srcxsl:value-of select=.//xsl:attribute /fo:external-graphic /fo:wrapper /xsl:for-each /fo:block : Then, I try to put another text block after the image block like this: fo:block page-break-before=avoid page-break-after=avoid xsl:for-each select=ADVICE/IMAGE fo:wrapper fo:external-graphic xsl:attribute name=srcxsl:value-of select=.//xsl:attribute /fo:external-graphic /fo:wrapper fo:wrapperTesting data line/fo:wrapper /xsl:for-each /fo:block fo:blockAnother testing data line/fo:block The first text 'Testing data line' can be shown just next to the each image sucessfully in the same page. However, the last text 'Another testing data line' cannot be shown in the same page with the last image, even the last image is so small. A page break is forced to appear just after the image. I have tried to use table cell for the display like this, fo:table fo:table-column column-width=20cm/ fo:table-body xsl:for-each select=ADVICE/IMAGE fo:table-row fo:table-cell display-align=center fo:block text-align=center fo:external-graphic display-align=center text-align=center xsl:attribute name=srcxsl:value-of select=.//xsl:attribute /fo:external-graphic /fo:block /fo:table-cell /fo:table-row /xsl:for-each /fo:table-body /fo:table But the result is still the same. On the other hand, I just put the same coding in the static content as region- before, it can be shown successfully without page break (I think it is still to region-before cannot be page break). Is it the internal problem of FOP? Anything we can do to help? SL - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 15048] - Unwanted page break after image linked by external-graphic in region body
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15048. 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=15048 Unwanted page break after image linked by external-graphic in region body --- Additional Comments From [EMAIL PROTECTED] 2002-12-04 04:49 --- Really, the biggest help would be to post a FO document (no XSL, just the FO...i.e. do your XML transformation and produce an FO document) and set of graphics that we can use as a test case. Also, you may wish to check out a more recent version of FOP and see if the issue recurrs. The test case is most important to us, however. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 15048] - Unwanted page break after image linked by external-graphic in region body
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15048. 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=15048 Unwanted page break after image linked by external-graphic in region body --- Additional Comments From [EMAIL PROTECTED] 2002-12-04 05:28 --- Created an attachment (id=4035) fo file - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 15048] - Unwanted page break after image linked by external-graphic in region body
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15048. 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=15048 Unwanted page break after image linked by external-graphic in region body --- Additional Comments From [EMAIL PROTECTED] 2002-12-04 05:31 --- Created an attachment (id=4037) image 1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 15048] - Unwanted page break after image linked by external-graphic in region body
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15048. 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=15048 Unwanted page break after image linked by external-graphic in region body --- Additional Comments From [EMAIL PROTECTED] 2002-12-04 05:31 --- Created an attachment (id=4038) image 2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 15048] - Unwanted page break after image linked by external-graphic in region body
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15048. 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=15048 Unwanted page break after image linked by external-graphic in region body --- Additional Comments From [EMAIL PROTECTED] 2002-12-04 05:31 --- Created an attachment (id=4039) image 3 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 15048] - Unwanted page break after image linked by external-graphic in region body
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15048. 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=15048 Unwanted page break after image linked by external-graphic in region body --- Additional Comments From [EMAIL PROTECTED] 2002-12-04 05:31 --- Created an attachment (id=4040) image 4 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 15048] - Unwanted page break after image linked by external-graphic in region body
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15048. 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=15048 Unwanted page break after image linked by external-graphic in region body --- Additional Comments From [EMAIL PROTECTED] 2002-12-04 05:34 --- I have attached the fo and images file for your reference. The reason that we use 20.3 rather 20.4 is we find that 20.4 has out of memory problem when removing the embed-file attribute from the userconfig.xml. We have to generate a pdf for muti-asian languages, therefore, we have to choose a lower version. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 14248] - 51-page FO example, could be added to the samples
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14248. 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=14248 51-page FO example, could be added to the samples --- Additional Comments From [EMAIL PROTECTED] 2002-12-04 06:16 --- I'm drowning in stuff to do this week, but if someone wants to improve/correct the example, feel free to do it! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP Servlet, contrib stuff and tutorial
On Tue, 2002-12-03 at 22:04, J.Pietschmann wrote: Keiron Liddle wrote: - move contrib/servlet to examples/servlet - move contrib/plan to examples/plan - move contrib/mathml to examples/mathml One of the purposes that these serve is to demonstrate how to write an extension and for FOP to pick it up in the classpath. This might take away that. Granted for plan and mathml, but the servlet sees real use, and getting it built easily may be in order. Okay, for the servlet. I wasn't thinking of that. In either case I personally expect source which can be of real use in the src tree rather than anywhere else, and I don't think it matters much if the written documentation points to examples/something or src/java/org/something/else, as long as it is distributed with the binary distro, and this shouldn't be too hard to arrange. Well for the extension examples. If someone wants to write their own extension, they get the directory then change the source code and a few other things and it is ready. If it is in the source tree (including the META-INF) it could make it much more difficult for someone to start with. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Alt-Design: Preliminary results FO tree build test
Oleg Tkachenko wrote: Peter B. West wrote: Herewith the preliminary results of running the alt.design FO tree build against the 51 page test document supplied by Bertrand. What is included in this measurement? I presume it's fo parsing, userconfig processing and fo tree buiding? Yes. It's rather interesting to compare it with the trunk code. But I believe we need real profiler software results to make any serious conclusions. It would be interesting. Peter -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
