DO NOT REPLY [Bug 17369] - Footnote duplication
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=17369. 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=17369 Footnote duplication --- Additional Comments From [EMAIL PROTECTED] 2003-02-27 09:28 --- The footnote duplication also occurs in 0.20.5rc2. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/apps TraxInputHandler.java XSLTInputHandler.java AWTStarter.java FOInputHandler.java CommandLineOptions.java InputHandler.java Version.java PrintStarter.java Fop.java LayoutHandler.java CommandLineStarter.java Driver.java FOPException.java Starter.java StructureHandler.java ErrorHandler.java
jeremias2003/02/27 02:13:08 Modified:src/org/apache/fop/apps TraxInputHandler.java XSLTInputHandler.java AWTStarter.java FOInputHandler.java CommandLineOptions.java InputHandler.java Version.java PrintStarter.java Fop.java LayoutHandler.java CommandLineStarter.java Driver.java FOPException.java Starter.java StructureHandler.java Removed: src/org/apache/fop/apps ErrorHandler.java Log: Switched to long licence Some general checkstyle fixing Removed unused ErrorHandler (readd when we know what to do with it) Revision ChangesPath 1.6 +72 -28xml-fop/src/org/apache/fop/apps/TraxInputHandler.java Index: TraxInputHandler.java === RCS file: /home/cvs/xml-fop/src/org/apache/fop/apps/TraxInputHandler.java,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- TraxInputHandler.java 21 Aug 2001 06:18:54 - 1.5 +++ TraxInputHandler.java 27 Feb 2003 10:13:04 - 1.6 @@ -1,12 +1,57 @@ /* * $Id$ - * Copyright (C) 2001 The Apache Software Foundation. All rights reserved. - * For details on use and redistribution please refer to the - * LICENSE file included with these sources. - */ - + * + *The Apache Software License, Version 1.1 + * + * + * Copyright (C) 1999-2003 The Apache Software Foundation. All rights reserved. + * + * Redistribution and use in source and binary forms, with or without modifica- + * tion, are permitted provided that the following conditions are met: + * + * 1. Redistributions of source code must retain the above copyright notice, + *this list of conditions and the following disclaimer. + * + * 2. Redistributions in binary form must reproduce the above copyright notice, + *this list of conditions and the following disclaimer in the documentation + *and/or other materials provided with the distribution. + * + * 3. The end-user documentation included with the redistribution, if any, must + *include the following acknowledgment: This product includes software + *developed by the Apache Software Foundation (http://www.apache.org/). + *Alternately, this acknowledgment may appear in the software itself, if + *and wherever such third-party acknowledgments normally appear. + * + * 4. The names FOP and Apache Software Foundation must not be used to + *endorse or promote products derived from this software without prior + *written permission. For written permission, please contact + *[EMAIL PROTECTED] + * + * 5. Products derived from this software may not be called Apache, nor may + *Apache appear in their name, without prior written permission of the + *Apache Software Foundation. + * + * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, + * INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND + * FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE + * APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, + * INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLU- + * DING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS + * OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON + * ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT + * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF + * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + * + * + * This software consists of voluntary contributions made by many individuals + * on behalf of the Apache Software Foundation and was originally created by + * James Tauber [EMAIL PROTECTED]. For more information on the Apache + * Software Foundation, please see http://www.apache.org/. + */ package org.apache.fop.apps; +// Imported java.io classes +import java.io.File; // Imported TraX classes import javax.xml.transform.TransformerFactory; @@ -15,44 +60,40 @@ import javax.xml.transform.sax.SAXSource; import javax.xml.transform.sax.SAXTransformerFactory; - // Imported SAX classes import org.xml.sax.InputSource; -import org.xml.sax.SAXException; import org.xml.sax.XMLReader; import org.xml.sax.XMLFilter; - - -// Imported java.io classes -import java.io.InputStream; -import java.io.IOException; -import java.io.File; - /** - * XSLTInputHandler basically takes an xmlfile
DO NOT REPLY [Bug 17472] New: - Images appear twice oin PDF output
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=17472. 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=17472 Images appear twice oin PDF output Summary: Images appear twice oin PDF output Product: Fop Version: 0.20.5 Platform: Sun OS/Version: Solaris Status: NEW Severity: Normal Priority: Other Component: images AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Although my fo-file has only one reference to an external image called Stack.png, this image appears twice in the final PDF output. fo:external-graphic src=url(Pictures/Stack.png) width=auto height=auto content-width=auto content-height=auto text-align=center/ I've searched for the string Stack.png in the whole fo-document and it appears only once in the document (in the element above), but the picture can be seen twice, one below the other Thios happend with *some* of my images, but not with all. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17472] - Images appear twice oin PDF output
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=17472. 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=17472 Images appear twice oin PDF output --- Additional Comments From [EMAIL PROTECTED] 2003-02-27 11:40 --- Could you please be more specific? Are you using tables or footnotes? It will help when you send your fo file - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17472] - Images appear twice oin PDF output
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=17472. 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=17472 Images appear twice oin PDF output --- Additional Comments From [EMAIL PROTECTED] 2003-02-27 12:03 --- Created an attachment (id=5075) FO-output by the DocBook XSLT stylesheets - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
en_US hyphenation pattern
Anyone know why the en_US hyphenation pattern was dropped in 0.20.5rc2? Thanks, Derrick This electronic transmission is strictly confidential to Smith Nephew and intended solely for the addressee. It may contain information which is covered by legal, professional or other privilege. If you are not the intended addressee, or someone authorized by the intended addressee to receive transmissions on behalf of the addressee, you must not retain, disclose in any form, copy or take any action in reliance on this transmission. If you have received this transmission in error, please notify the sender as soon as possible and destroy this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: en_US hyphenation pattern
Licensing issues. Koes, Derrick wrote: Anyone know why the en_US hyphenation pattern was dropped in 0.20.5rc2? Thanks, Derrick -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Wrong operand type error in ASV 3.0
Hi All, I have written a small svg document and embedding this svg document in an FO document to covert to pdf. I guess the FOP completely depends on batik for SVG2PDF conversion. When I try to open the resulting pdf, it says wrong operand type. Can anybody help ? Thanks in advance, Swapan. ?xml version=1.0 encoding=UTF-8? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master margin-right=1.5cm margin-left=1.5cm margin-bottom=2cm margin-top=1cm page-width=21cm page-height=29.7cm master-name=first fo:region-body margin-top=0cm margin-bottom=0cm/ fo:region-before extent=0cm/ fo:region-after extent=0cm/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=first fo:static-content flow-name=xsl-region-before fo:block line-height=14pt font-size=10pt text-align=endEmbedding SVG examples/fo:block /fo:static-content fo:static-content flow-name=xsl-region-after fo:block line-height=14pt font-size=10pt text-align=endPage fo:page-number//fo:block /fo:static-content fo:flow flow-name=xsl-region-body fo:block fo:instream-foreign-object svg:svg width=16.1925cm height=20.955cm viewBox=0 0 8.5 11 version=1.1 xmlns:svg=http://www.w3.org/2000/svg; svg:g transform=matrix(1 0 0 1 0 0) /svg:g svg:g transform=matrix(0.01041667 0 0 0.01041667 0 0) svg:text x=48 y=108 font-family=Times New Roman font- size=20pt font-weight=bold fill=#00 stroke=none text- anchor=start svg:tspan x=48 y=108 textLength=57 ABC/svg:tspan svg:tspan x=116 y=108 textLength=114 Company/svg:tspan /svg:text svg:text x=628 y=66.53516 font-family=Times New Roman font- size=15.6pt fill=#00 stroke=none text-anchor=start svg:tspan x=628 y=66.53516 O/svg:tspan /svg:text svg:text x=644 y=66.53516 font-family=Times New Roman font- size=12pt fill=#00 stroke=none text-anchor=start svg:tspan x=644 y=66.53516 textLength=107 RGANIZATION/svg:tspan /svg:text !-- If I remove this line, everything seems to work fine -- svg:line x1=58 y1=179 x2=403 y2=179 stroke=#00 stroke- width=0.5 / /svg:g /svg:svg /fo:instream-foreign-object /fo:block /fo:flow /fo:page-sequence /fo:root __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Licence for XSL-FO schema
Licence for XSL-FO schema Jeremias Maerki [EMAIL PROTECTED] Date: Tue, 25 Feb 2003 16:57:33 +0100 Is it safe to believe that we can add the Apache licence to the XSL-FO schema from Chuck Paussa? Or does he also have to do an explicit copyright transfer, first? Please add an Apache license to the XSL-FO schema that I developed. There are no other legal encumbrances on that document. Chuck Paussa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
A weekly/monthly redesign bulletin? (Was: keep propery)
Jeremias Maerki [EMAIL PROTECTED]: ... Check the FOP website regularly for the status of the redesign. To stave off the biggest FOP FAQ after doesn't keep-* work in Fop?, ie. what's the schedule for the redesign?, could it perhaps be an idea to post a weekly bulletin on the devel list? Just a very short message eg. something like this: Subject: FOP redesign bulletin, week #30, 2003 Work done this week: - improvement of font metrics - made to work with IBM Java VM - blah. blah. Work planned for next week: - more font metrics improvements - make it work with gcj - blah. blah. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: XMLReader...
Swapan Golla wrote: Any ways to instruct FOP to use a particular SAXParser rather than setting as system property ? FOP uses whatever parser you supply to the Driver, however, providing a certain parser to external SVG is a bit trickier. The only way I can see right now is to get the source distro, adjust the createParser() method of the Driver appropriately and recompile. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: A weekly/monthly redesign bulletin? (Was: keep propery)
Do you volunteer? :-) Monitoring the CVS activity (fop-cvs list), the fop-dev list and the CHANGES/status.xml files in CVS should give you a good idea what's going on. We could you some help, even if it's just writing something like a weekly bulletin. http://cvs.apache.org/viewcvs.cgi/xml-fop/CHANGES http://cvs.apache.org/viewcvs.cgi/xml-fop/status.xml On 27.02.2003 20:33:26 Steinar Bang wrote: Jeremias Maerki [EMAIL PROTECTED]: ... Check the FOP website regularly for the status of the redesign. To stave off the biggest FOP FAQ after doesn't keep-* work in Fop?, ie. what's the schedule for the redesign?, could it perhaps be an idea to post a weekly bulletin on the devel list? Just a very short message eg. something like this: Subject: FOP redesign bulletin, week #30, 2003 Work done this week: - improvement of font metrics - made to work with IBM Java VM - blah. blah. Work planned for next week: - more font metrics improvements - make it work with gcj - blah. blah. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: HTML to FO
Hi, Could you give some more information on where I can get hold of this tool. I did a search for htmlfo on Google and found a stylesheet that is in some other langauage to do with DSSSL. Ken there is a tool called htmlfo which does that.. -Original Message- From: Swapan Golla [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 1:04 PM To: [EMAIL PROTECTED] Subject: HTML to FO I am having a need to convert html ( or xhtml ) to fo documents and then to pdf. Any suggestions on the best ways to achieve this ? I should be able to use/call this from my java program. Thanks in advance, Swapan. _ Express yourself with cool emoticons http://messenger.msn.co.uk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: HTML to FO
big blue has a stylesheet that does a ok job at it. It's probably a good starting point if you have clean xhtml conversion guide http://www-106.ibm.com/developerworks/library/x-xslfo2app/ stylesheet http://www-106.ibm.com/developerworks/library/x-xslfo2app/xhtml-to-xslfo.xsl JohnPT Ken Masters [EMAIL PROTECTED] 02/27/2003 03:44 PM Please respond to fop-dev To:[EMAIL PROTECTED] cc: Subject:RE: HTML to FO Hi, Could you give some more information on where I can get hold of this tool. I did a search for htmlfo on Google and found a stylesheet that is in some other langauage to do with DSSSL. Ken there is a tool called htmlfo which does that.. -Original Message- From: Swapan Golla [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 1:04 PM To: [EMAIL PROTECTED] Subject: HTML to FO I am having a need to convert html ( or xhtml ) to fo documents and then to pdf. Any suggestions on the best ways to achieve this ? I should be able to use/call this from my java program. Thanks in advance, Swapan. _ Express yourself with cool emoticons http://messenger.msn.co.uk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: A weekly/monthly redesign bulletin? (Was: keep propery)
Jeremias Maerki [EMAIL PROTECTED]: ... Check the FOP website regularly for the status of the redesign. To stave off the biggest FOP FAQ after doesn't keep-* work in Fop?, ie. what's the schedule for the redesign?, could it perhaps be an idea to post a weekly bulletin on the devel list? Just a very short message eg. something like this: Subject: FOP redesign bulletin, week #30, 2003 Work done this week: - improvement of font metrics - made to work with IBM Java VM - blah. blah. Work planned for next week: - make it work with gcj FYII just got a patched gcj 3.3 (compiling an exe) working with a cutdown of the code. I think that gcj needs some work before it will be really useful. Keiron. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/layoutmgr AbstractLayoutManager.java LayoutManager.java BlockLayoutManager.java BlockContainerLayoutManager.java StaticContentLayoutManager.java PageLayoutManager.java ContentLayoutManager.java
keiron 2003/02/27 15:30:51
Modified:src/org/apache/fop/area PageViewport.java
src/org/apache/fop/layoutmgr AbstractLayoutManager.java
LayoutManager.java BlockLayoutManager.java
BlockContainerLayoutManager.java
StaticContentLayoutManager.java
PageLayoutManager.java ContentLayoutManager.java
Log:
improvement on markers, don't know if it is correct
Revision ChangesPath
1.15 +68 -43xml-fop/src/org/apache/fop/area/PageViewport.java
Index: PageViewport.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/area/PageViewport.java,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- PageViewport.java 20 Feb 2003 02:47:44 - 1.14
+++ PageViewport.java 27 Feb 2003 23:30:47 - 1.15
@@ -47,8 +47,9 @@
// start and end are added by the fo that contains the markers
private Map markerFirstStart = null;
private Map markerLastStart = null;
-private Map markerFirstEnd = null;
+private Map markerFirstAny = null;
private Map markerLastEnd = null;
+private Map markerLastAny = null;
/**
* Create a page viewport.
@@ -185,8 +186,8 @@
* For first-starting-within-page it adds the markers
* that are starting only if the marker class name is not
* already added.
- * For first-including-carryover it adds any marker if
- * the marker class name is not already added.
+ * For first-including-carryover it adds any starting marker
+ * if the marker class name is not already added.
* For last-starting-within-page it adds all marks that
* are starting, replacing earlier markers.
* For last-ending-within-page it adds all markers that
@@ -196,44 +197,58 @@
*
* @param marks the map of markers to add
* @param start if the area being added is starting or ending
+ * @param isfirst isfirst or islast flag
*/
-public void addMarkers(Map marks, boolean start) {
+public void addMarkers(Map marks, boolean start, boolean isfirst) {
if (start) {
-if (markerFirstStart == null) {
-markerFirstStart = new HashMap();
-}
-if (markerLastStart == null) {
-markerLastStart = new HashMap();
-}
-if (markerFirstEnd == null) {
-markerFirstEnd = new HashMap();
-}
-// only put in new values, leave current
-for (Iterator iter = marks.keySet().iterator(); iter.hasNext();) {
-Object key = iter.next();
-if (!markerFirstStart.containsKey(key)) {
-markerFirstStart.put(key, marks.get(key));
+if (isfirst) {
+if (markerFirstStart == null) {
+markerFirstStart = new HashMap();
}
-if (!markerFirstEnd.containsKey(key)) {
-markerFirstEnd.put(key, marks.get(key));
+if (markerFirstAny == null) {
+markerFirstAny = new HashMap();
+}
+// only put in new values, leave current
+for (Iterator iter = marks.keySet().iterator(); iter.hasNext();) {
+Object key = iter.next();
+if (!markerFirstStart.containsKey(key)) {
+markerFirstStart.put(key, marks.get(key));
+}
+if (!markerFirstAny.containsKey(key)) {
+markerFirstAny.put(key, marks.get(key));
+}
+}
+if (markerLastStart == null) {
+markerLastStart = new HashMap();
+}
+// replace all
+markerLastStart.putAll(marks);
+
+} else {
+if (markerFirstAny == null) {
+markerFirstAny = new HashMap();
+}
+// only put in new values, leave current
+for (Iterator iter = marks.keySet().iterator(); iter.hasNext();) {
+Object key = iter.next();
+if (!markerFirstAny.containsKey(key)) {
+markerFirstAny.put(key, marks.get(key));
+}
}
}
-markerLastStart.putAll(marks);
} else {
-if (markerFirstEnd == null) {
-markerFirstEnd = new HashMap();
-}
-if (markerLastEnd == null) {
-markerLastEnd = new HashMap();
-}
-// only put in new values, leave current
Re: markers in redesign
Hi all, I think I am getting an idea of the markers with Peter's and others points but I don't fully understand how it should work or be implemented. Anyway I have committed the code of how it might roughly work and hopefully it is correct for the containing page. It isn't that much code anyway, it is mainly a matter of getting the logic right. When we know how it definitely should work then we can adjust it if necessary. Keiron. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Wrong operand type error in ASV 3.0
!-- If I remove this line, everything seems to work fine -- svg:line x1=58 y1=179 x2=403 y2=179 stroke=#00 stroke- width=0.5 / IIRC It is probably an error caused by this line being 0.5 width. In PDF lines can only be whole numbers and it might wrongly be inserting 0.5 in the PDF causing the error. Try making it width 1. If you need a 0.5 width line it can be scaled. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
layout manager interface
Hi all, In order to make things more modular I would like to split the layout manager interface into two parts. One part that is used in the creation from the FO tree and another that is used by the implementations in order to do the actual layout. This should eventually make it possible to have different layout implementations. For now it shoud help make it a bit clearer and I want to have a go at trying the ideas I have for doing the layout in a slightly different way. I will call it LayoutProcessor unless there is a better idea. Any objections? Keiron. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: markers in redesign
Keiron Liddle wrote: Hi all, I think I am getting an idea of the markers with Peter's and others points but I don't fully understand how it should work or be implemented. Anyway I have committed the code of how it might roughly work and hopefully it is correct for the containing page. It isn't that much code any-way, it is mainly a matter of getting the logic right. When we know how it definitely should work then we can adjust it if necessary. Keiron, I have a couple of notes concerning markers in my posting on alt.design integration. What helped me in coming to terms with them was considering the simple usage of dictionary headings. The static-content will be the same on every page, extracting the first and last words defined on the page. On every page, though, the result will be different. I don't have the imagination for use cases for other situations, but one can easily envisage a case where page n and page n+1 retrieve the same marker; page n from the containing-page, and page n+1 from the previous page. -- 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: layout manager interface
Keiron Liddle wrote: Hi all, In order to make things more modular I would like to split the layout manager interface into two parts. One part that is used in the creation from the FO tree and another that is used by the implementations in order to do the actual layout. See my notes on the relationship between FO tree buildng and layout. In my view, the FO expressions cannot, in certain circumstances, and therefore in general, be *parsed* until the layout of their enclosing areas has occurred. The description in the spec of discrete processes of FO tree and area tree building is simply wrong and grossly misleading. This should eventually make it possible to have different layout implementations. For now it shoud help make it a bit clearer and I want to have a go at trying the ideas I have for doing the layout in a slightly different way. As long as the information path from the layout implementation back through the FO tree/layout interface to the FO tree builder is defined. I will call it LayoutProcessor unless there is a better idea. -- 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: layout manager interface
Keiron Liddle wrote: Hi all, In order to make things more modular I would like to split the layout manager interface into two parts. One part that is used in the creation from the FO tree and another that is used by the implementations in order to do the actual layout. See my notes on the relationship between FO tree buildng and layout. In my view, the FO expressions cannot, in certain circumstances, and therefore in general, be *parsed* until the layout of their enclosing areas has occurred. The description in the spec of discrete processes of FO tree and area tree building is simply wrong and grossly misleading. I have had a quick read and there should be no problem. This doesn't effect what the layout manager implementations see, only what the FO tree sees when creating the managers. If you need to put a call back or call a method on the FO tree it will still be possible. As long as the information path from the layout implementation back through the FO tree/layout interface to the FO tree builder is defined. It will remain as possible as it is know. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
