cvs commit: xml-fop/src/org/apache/fop/pdf FlateFilter.java PDFColor.java
keiron 2003/02/18 21:55:25
Modified:src/org/apache/fop/pdf FlateFilter.java PDFColor.java
Log:
fixed some minor errors
Revision ChangesPath
1.6 +7 -7 xml-fop/src/org/apache/fop/pdf/FlateFilter.java
Index: FlateFilter.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/pdf/FlateFilter.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- FlateFilter.java 17 Sep 2002 09:20:57 - 1.5
+++ FlateFilter.java 19 Feb 2003 05:55:25 - 1.6
@@ -135,8 +135,8 @@
* @param predictor the predictor to use
* @throws PDFFilterException if there is an error with the predictor
*/
-public void setPredictor(int predictor) throws PDFFilterException {
-predictor = predictor;
+public void setPredictor(int pred) throws PDFFilterException {
+predictor = pred;
}
@@ -155,9 +155,9 @@
* @param colors the colors to use
* @throws PDFFilterException if predictor is not PREDICTION_NONE
*/
-public void setColors(int colors) throws PDFFilterException {
+public void setColors(int cols) throws PDFFilterException {
if (predictor != PREDICTION_NONE) {
-colors = colors;
+colors = cols;
} else {
throw new PDFFilterException(
"Prediction must not be PREDICTION_NONE in"
@@ -205,9 +205,9 @@
* @param columns the number of columns to use for the filter
* @throws PDFFilterException if predictor is not PREDICTION_NONE
*/
-public void setColumns(int columns) throws PDFFilterException {
+public void setColumns(int cols) throws PDFFilterException {
if (predictor != PREDICTION_NONE) {
-columns = columns;
+columns = cols;
} else {
throw new PDFFilterException(
"Prediction must not be PREDICTION_NONE in"
1.16 +6 -6 xml-fop/src/org/apache/fop/pdf/PDFColor.java
Index: PDFColor.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/pdf/PDFColor.java,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- PDFColor.java 11 Jan 2003 19:38:52 - 1.15
+++ PDFColor.java 19 Feb 2003 05:55:25 - 1.16
@@ -314,9 +314,9 @@
this.green = 1.0 - this.green;
this.blue = 1.0 - this.yellow;
-this.red = (this.black / this.blackFactor) + this.red;
-this.green = (this.black / this.blackFactor) + this.green;
-this.blue = (this.black / this.blackFactor) + this.blue;
+this.red = (this.black / PDFColor.blackFactor) + this.red;
+this.green = (this.black / PDFColor.blackFactor) + this.green;
+this.blue = (this.black / PDFColor.blackFactor) + this.blue;
}
@@ -381,7 +381,7 @@
tempDouble = this.yellow;
}
-this.black = (tempDouble / this.blackFactor);
+this.black = (tempDouble / PDFColor.blackFactor);
}
@@ -402,7 +402,7 @@
tempDouble = this.blue;
}
-this.black = 1.0 - (tempDouble / this.blackFactor);
+this.black = 1.0 - (tempDouble / PDFColor.blackFactor);
}
/**
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/fo/flow RetrieveMarker.java
keiron 2003/02/18 21:54:15
Modified:src/org/apache/fop/fo/flow RetrieveMarker.java
Log:
add retrieve marker layout manager
Revision ChangesPath
1.12 +31 -10xml-fop/src/org/apache/fop/fo/flow/RetrieveMarker.java
Index: RetrieveMarker.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/flow/RetrieveMarker.java,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- RetrieveMarker.java 20 Jun 2002 09:14:13 - 1.11
+++ RetrieveMarker.java 19 Feb 2003 05:54:15 - 1.12
@@ -1,6 +1,6 @@
/*
* $Id$
- * Copyright (C) 2001 The Apache Software Foundation. All rights reserved.
+ * Copyright (C) 2001-2003 The Apache Software Foundation. All rights reserved.
* For details on use and redistribution please refer to the
* LICENSE file included with these sources.
*/
@@ -8,27 +8,39 @@
package org.apache.fop.fo.flow;
// FOP
-import org.apache.fop.fo.*;
-import org.apache.fop.fo.properties.*;
-import org.apache.fop.layout.*;
-import org.apache.fop.datatypes.*;
import org.apache.fop.apps.FOPException;
-
-// Java
-import java.util.Vector;
-
+import org.apache.fop.fo.FONode;
+import org.apache.fop.fo.FObjMixed;
+import org.apache.fop.layoutmgr.RetrieveMarkerLayoutManager;
import org.xml.sax.Attributes;
+import java.util.List;
+
+/**
+ * The retrieve-marker formatting object.
+ * This will create a layout manager that will retrieve
+ * a marker based on the information.
+ */
public class RetrieveMarker extends FObjMixed {
private String retrieveClassName;
private int retrievePosition;
private int retrieveBoundary;
+/**
+ * Create a retrieve marker object.
+ *
+ * @see org.apache.fop.fo.FONode#FONode(FONode)
+ */
public RetrieveMarker(FONode parent) {
super(parent);
}
+/**
+ * Handle the attributes for the retrieve-marker.
+ *
+ * @see org.apache.fop.fo.FONode#handleAttrs(Attributes)
+ */
public void handleAttrs(Attributes attlist) throws FOPException {
super.handleAttrs(attlist);
this.retrieveClassName =
@@ -39,4 +51,13 @@
this.properties.get("retrieve-boundary").getEnum();
}
+public void addLayoutManager(List lms) {
+RetrieveMarkerLayoutManager rmlm;
+rmlm = new RetrieveMarkerLayoutManager(retrieveClassName,
+retrievePosition,
+retrieveBoundary);
+rmlm.setUserAgent(getUserAgent());
+rmlm.setFObj(this);
+lms.add(rmlm);
+}
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/fo/pagination Region.java
keiron 2003/02/18 21:51:15
Modified:src/org/apache/fop/fo/flow ExternalGraphic.java
src/org/apache/fop/fo/pagination Region.java
Log:
use trait setter for setting traits
Revision ChangesPath
1.31 +4 -4 xml-fop/src/org/apache/fop/fo/flow/ExternalGraphic.java
Index: ExternalGraphic.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/flow/ExternalGraphic.java,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- ExternalGraphic.java 14 Feb 2003 04:15:04 - 1.30
+++ ExternalGraphic.java 19 Feb 2003 05:51:15 - 1.31
@@ -23,8 +23,8 @@
import org.apache.fop.image.ImageFactory;
import org.apache.fop.image.FopImage;
import org.apache.fop.area.inline.InlineArea;
-import org.apache.fop.layoutmgr.AbstractLayoutManager;
import org.apache.fop.layoutmgr.LeafNodeLayoutManager;
+import org.apache.fop.layoutmgr.TraitSetter;
import org.apache.fop.area.inline.Image;
import org.apache.fop.area.inline.Viewport;
import org.apache.fop.datatypes.Length;
@@ -104,8 +104,8 @@
// Common Border, Padding, and Background Properties
BorderAndPadding bap = propMgr.getBorderAndPadding();
BackgroundProps bProps = propMgr.getBackgroundProps();
-AbstractLayoutManager.addBorders(vp, bap);
-AbstractLayoutManager.addBackground(vp, bProps);
+TraitSetter.addBorders(vp, bap);
+TraitSetter.addBackground(vp, bProps);
return vp;
}
1.17 +4 -4 xml-fop/src/org/apache/fop/fo/pagination/Region.java
Index: Region.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/pagination/Region.java,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- Region.java 5 Jan 2003 22:07:03 - 1.16
+++ Region.java 19 Feb 2003 05:51:15 - 1.17
@@ -21,7 +21,7 @@
import org.apache.fop.area.CTM;
import org.apache.fop.area.RegionViewport;
import org.apache.fop.area.RegionReference;
-import org.apache.fop.layoutmgr.AbstractLayoutManager;
+import org.apache.fop.layoutmgr.TraitSetter;
// SAX
import org.xml.sax.Attributes;
@@ -101,8 +101,8 @@
// Common Border, Padding, and Background Properties
BorderAndPadding bap = propMgr.getBorderAndPadding();
BackgroundProps bProps = propMgr.getBackgroundProps();
-AbstractLayoutManager.addBorders(r, bap);
-AbstractLayoutManager.addBackground(r, bProps);
+TraitSetter.addBorders(r, bap);
+TraitSetter.addBackground(r, bProps);
// this.properties.get("clip");
// this.properties.get("display-align");
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/layoutmgr/table Body.java Caption.java Cell.java Column.java Row.java TableAndCaptionLayoutManager.java TableLayoutManager.java
keiron 2003/02/18 21:49:29
Modified:src/org/apache/fop/layoutmgr AbstractLayoutManager.java
BlockContainerLayoutManager.java
BlockLayoutManager.java
BlockStackingLayoutManager.java
BreakPossPosIter.java ContentLayoutManager.java
FlowLayoutManager.java
InlineStackingLayoutManager.java LayoutManager.java
LeafNodeLayoutManager.java LineLayoutManager.java
MinOptMax.java PageLayoutManager.java
StaticContentLayoutManager.java
TextLayoutManager.java TraitSetter.java
src/org/apache/fop/layoutmgr/list Item.java
ListBlockLayoutManager.java
ListItemLayoutManager.java
src/org/apache/fop/layoutmgr/table Body.java Caption.java
Cell.java Column.java Row.java
TableAndCaptionLayoutManager.java
TableLayoutManager.java
Added: src/org/apache/fop/layoutmgr
RetrieveMarkerLayoutManager.java
Log:
add and retrive markers
use trait setter for area traits
some style cleanups
Revision ChangesPath
1.21 +23 -65xml-fop/src/org/apache/fop/layoutmgr/AbstractLayoutManager.java
Index: AbstractLayoutManager.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/layoutmgr/AbstractLayoutManager.java,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- AbstractLayoutManager.java14 Feb 2003 04:15:07 - 1.20
+++ AbstractLayoutManager.java19 Feb 2003 05:49:28 - 1.21
@@ -9,18 +9,16 @@
import org.apache.fop.fo.FObj;
import org.apache.fop.fo.FOUserAgent;
+import org.apache.fop.fo.flow.Marker;
import org.apache.fop.area.Area;
import org.apache.fop.area.Resolveable;
import org.apache.fop.area.PageViewport;
import org.apache.fop.fo.PropertyManager;
-import org.apache.fop.area.Trait;
-import org.apache.fop.layout.BorderAndPadding;
-import org.apache.fop.layout.BackgroundProps;
-import org.apache.fop.traits.BorderProps;
import org.apache.avalon.framework.logger.Logger;
import java.util.ListIterator;
+import java.util.Map;
/**
* The base class for all LayoutManagers.
@@ -30,6 +28,7 @@
protected LayoutManager parentLM = null;
protected FObj fobj;
protected String foID = null;
+protected Map markers = null;
/** True if this LayoutManager has handled all of its content. */
private boolean bFinished = false;
@@ -37,7 +36,6 @@
protected ListIterator childLMiter;
protected boolean bInited = false;
-
/**
* Abstract layout manager.
*/
@@ -52,6 +50,7 @@
public void setFObj(FObj fo) {
this.fobj = fo;
foID = fobj.getID();
+markers = fobj.getMarkers();
childLMiter = new LMiter(fobj.getChildren());
}
@@ -64,6 +63,11 @@
userAgent = ua;
}
+/**
+ * Get the user agent.
+ *
+ * @see org.apache.fop.layoutmgr.LayoutManager#getUserAgent()
+ */
public FOUserAgent getUserAgent() {
return userAgent;
}
@@ -318,12 +322,22 @@
}
/**
+ * Add the markers when adding an area.
+ */
+protected void addMarkers(boolean start) {
+// add markers
+if (markers != null) {
+addMarkerMap(markers, start);
+}
+}
+
+/**
* Delegate adding marker to the parent layout manager.
*
* @see org.apache.fop.layoutmgr.LayoutManager
*/
-public void addMarker(String name, LayoutManager lm, boolean start) {
-parentLM.addMarker(name, lm, start);
+public void addMarkerMap(Map marks, boolean start) {
+parentLM.addMarkerMap(marks, start);
}
/**
@@ -331,65 +345,9 @@
*
* @see org.apache.fop.layoutmgr.LayoutManager
*/
-public LayoutManager retrieveMarker(String name, int pos, int boundary) {
+public Marker retrieveMarker(String name, int pos, int boundary) {
return parentLM.retrieveMarker(name, pos, boundary);
}
-/**
- * Add borders to an area.
- * Layout managers that create areas with borders can use this to
- * add the borders to the area.
- */
-public static void addBorders(Area curBlock, BorderAndPadding bordProps) {
-BorderProps bps = getBorderProps(bordProps, BorderAndPadding.TOP);
-if(bps.width != 0) {
-curBlock.addTrait(Trait.BORDER_BEFORE, bps);
-}
-bps = getBorderProps(bordProps, BorderAndPadding.BOTTOM);
cvs commit: xml-fop/src/org/apache/fop/area Page.java PageViewport.java
keiron 2003/02/18 21:43:25
Modified:src/org/apache/fop/area Page.java PageViewport.java
Log:
place markers on page viewport
Revision ChangesPath
1.9 +1 -6 xml-fop/src/org/apache/fop/area/Page.java
Index: Page.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/area/Page.java,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- Page.java 19 Dec 2002 00:35:31 - 1.8
+++ Page.java 19 Feb 2003 05:43:24 - 1.9
@@ -29,11 +29,6 @@
private RegionViewport regionEnd = null;
private RegionViewport regionAfter = null;
-// hashmap of markers for this page
-// start and end are added by the fo that contains the markers
-private Map markerStart = null;
-private Map markerEnd = null;
-
// temporary map of unresolved objects used when serializing the page
private Map unresolved = null;
1.13 +32 -1 xml-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.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- PageViewport.java 27 Jan 2003 09:24:24 - 1.12
+++ PageViewport.java 19 Feb 2003 05:43:24 - 1.13
@@ -41,6 +41,11 @@
private Map pendingResolved = null;
+// hashmap of markers for this page
+// start and end are added by the fo that contains the markers
+private Map markerStart = null;
+private Map markerEnd = null;
+
/**
* Create a page viewport.
* @param p the page reference area that holds the contents
@@ -168,6 +173,32 @@
unresolved = null;
}
}
+}
+
+/**
+ * Add the start markers for this page.
+ *
+ * @param marks the map of start markers to add
+ */
+public void addMarkers(Map marks, boolean start) {
+if (start) {
+if (markerStart == null) {
+markerStart = new HashMap();
+}
+markerStart.putAll(marks);
+} else {
+if (markerEnd == null) {
+markerEnd = new HashMap();
+}
+markerEnd.putAll(marks);
+}
+}
+
+public Object getMarker(String name, int pos) {
+if (markerStart != null) {
+return markerStart.get(name);
+}
+return null;
}
/**
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/fo/flow InstreamForeignObject.java
keiron 2003/02/18 21:39:20
Modified:src/org/apache/fop/fo/flow InstreamForeignObject.java
Log:
cleaned up some styling
Revision ChangesPath
1.36 +50 -43xml-fop/src/org/apache/fop/fo/flow/InstreamForeignObject.java
Index: InstreamForeignObject.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/flow/InstreamForeignObject.java,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- InstreamForeignObject.java14 Feb 2003 04:15:04 - 1.35
+++ InstreamForeignObject.java19 Feb 2003 05:39:20 - 1.36
@@ -1,6 +1,6 @@
/*
* $Id$
- * Copyright (C) 2001 The Apache Software Foundation. All rights reserved.
+ * Copyright (C) 2001-2003 The Apache Software Foundation. All rights reserved.
* For details on use and redistribution please refer to the
* LICENSE file included with these sources.
*/
@@ -8,54 +8,54 @@
package org.apache.fop.fo.flow;
// FOP
-import org.apache.fop.fo.*;
-import org.apache.fop.fo.properties.*;
-import org.apache.fop.datatypes.Length;
-import org.apache.fop.area.Area;
-import org.apache.fop.area.inline.InlineArea;
-import org.apache.fop.area.inline.Viewport;
+import java.awt.geom.Point2D;
+import java.awt.geom.Rectangle2D;
+import java.util.List;
+
import org.apache.fop.area.inline.ForeignObject;
-import org.apache.fop.layout.FontState;
+import org.apache.fop.area.inline.Viewport;
+import org.apache.fop.datatypes.Length;
+import org.apache.fop.fo.FONode;
+import org.apache.fop.fo.FObj;
+import org.apache.fop.fo.XMLObj;
+import org.apache.fop.fo.properties.DisplayAlign;
+import org.apache.fop.fo.properties.Overflow;
+import org.apache.fop.fo.properties.Scaling;
+import org.apache.fop.fo.properties.TextAlign;
import org.apache.fop.layout.AccessibilityProps;
import org.apache.fop.layout.AuralProps;
-import org.apache.fop.layout.BorderAndPadding;
import org.apache.fop.layout.BackgroundProps;
+import org.apache.fop.layout.BorderAndPadding;
import org.apache.fop.layout.MarginInlineProps;
import org.apache.fop.layout.RelativePositionProps;
-import org.apache.fop.apps.FOPException;
-import org.apache.fop.layoutmgr.LayoutManager;
import org.apache.fop.layoutmgr.LeafNodeLayoutManager;
-
import org.w3c.dom.Document;
-import java.awt.geom.Point2D;
-import java.awt.geom.Rectangle2D;
-import java.util.List;
-
+/**
+ * The instream-foreign-object flow formatting object.
+ * This is an atomic inline object that contains
+ * xml data.
+ */
public class InstreamForeignObject extends FObj {
-int breakBefore;
-int breakAfter;
-int spaceBefore;
-int spaceAfter;
-int startIndent;
-int endIndent;
-
-Viewport areaCurrent;
+private Viewport areaCurrent;
/**
* constructs an instream-foreign-object object (called by Maker).
*
* @param parent the parent formatting object
- * @param propertyList the explicit properties of this object
*/
public InstreamForeignObject(FONode parent) {
super(parent);
}
+/**
+ * Add the layout manager for this into the list.
+ * @see org.apache.fop.fo.FObj#addLayoutManager(List)
+ */
public void addLayoutManager(List list) {
areaCurrent = getInlineArea();
-if(areaCurrent != null) {
+if (areaCurrent != null) {
LeafNodeLayoutManager lm = new LeafNodeLayoutManager();
lm.setUserAgent(getUserAgent());
lm.setFObj(this);
@@ -68,6 +68,8 @@
/**
* Get the inline area created by this element.
+ *
+ * @return the viewport inline area
*/
protected Viewport getInlineArea() {
if (children == null) {
@@ -79,7 +81,7 @@
return null;
}
FONode fo = (FONode)children.get(0);
-if(!(fo instanceof XMLObj)) {
+if (!(fo instanceof XMLObj)) {
// error
return null;
}
@@ -115,14 +117,14 @@
int bpd = -1;
int ipd = -1;
boolean bpdauto = false;
-if(hasLH) {
+if (hasLH) {
bpd = properties.get("line-height").getLength().mvalue();
} else {
// this property does not apply when the line-height applies
// isn't the block-progression-dimension always in the same
// direction as the line height?
len = properties.get("block-progression-dimension.optimum").getLength();
-if(!len.isAuto()) {
+if (!len.isAuto()) {
bpd = len.mvalue();
} else {
len = properties.get("height").getLength();
@@ -133,11 +135,11 @@
}
markers in redesign
Hi all, Since the topic is being discussed why don't we look at implementing markers in the redesign. I'll try to do what is obvious, getting the markers from the fo, adding when adding areas and retrieving when needed. I think some areas need changing so that the layout manager type is resolved after resolving markers, for example with tables it shouldn't make any assumptions about the type of child. I don't understand the boundaries etc. so I might need some help there. Keiron. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Markers in areas
Mark C. Allman wrote: ... but markers will continue to work as per the XSLFO spec, correct? There are restrictions (and have always been). Look into the CHANGES file. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Licence issues in hyphenation patterns
[EMAIL PROTECTED] wrote: I didn't modify the old pt.xml file, I wrote a new one entirely from scratch. ... Sorry for being unclear and short-spoken, I didn't meant to offend you. However, did you really start with an empty file in an editor and typed in all the pattern strings? The issues are as follows. There are Original Works. If someone creates a new file by typing stuff into an editor he creates an Original Work. Running the hyphenation pattern programm on a properly marked up dictionary or corpus is probably also creating an Original Work, with certain caveats (it wasn't, for example, if the dictionary was marked up by someone else for the sole purpose of serving as input for the hyphenation pattern program). Mechanically transforming an Original Work creates another represenation of this work, for example changing Unix LF to DOS CRLF, or changing ISO-8859-9 encoding into UTF-8 encoding. You can't claim copyright to the result of such a transformation. In order to claim copyright you have to do some non-trivial processing, preferably involving some manual work. This creates a Derived Work (unless you mutilated the original thouroughly enough that you again created an Original Work). Whether cut&paste significant portions of a TeX hyphenation file into a thin XML frame can be considered a Mechanical Transformation or whether it is non-trivial enough to make a Derived Work has yet to be decided in court. Adding hyphenation exceptions should suffice though. Anyway, I suppose you can claim copyright for the file you submitted. This is, however, not yet the end of the story. Again, you probably used some data to derive the patterns, be it a corpus or a TeX file. You'll have to check (and/or decide) whether you produced an Original Work, i.e. you did by far the most work yourself, and none of your data sources prohibited you by any means to perform this work, or whether you created a Derived Work. In the second case, the license of your source data may place restrictions on your work in case you want to have it distributed (nobody can prevent you from using basically anything in private). For example, if you used an LPPL'd TeX file as source, you can choose the license of your work (LPPL isn't as viral as GPL), but you can't place it for example under APL because of the file name restriction. You are forced to either put your work under LPPL again, or an amended APL, or roll your own. This is *still* not everything. You supplied a whole file, not a patch. In this file you generously transferred your copyright to the ASF (this fact crept into my brain only after I committed the file). You have to be legally entitled to do so. If making file was part of your work, or related to your work, you should check your contract whether you can claim copyright for your work yourself and do what you want with it, common practice is that by signing your contract you give up everything to your employer. In this case the ASF needs a paper signed by you and your boss which explicitely states that the copyright for the file was assigned to the ASF. You can find a template here http://jakarta.apache.org/site/agreement.html Note that small patches are different, in this case I as a committer create a Derived Work, and unless you as the patch submitter put a viral licence into it, I can put the result under APL (implicitely), and I already have sent in a paper assigning my copyright away. Well, to keep it short, I'd vote to spare you the paperwork if you tell us that you have the right to put the file under the Apache license and assign the copyright to the ASF (you can keep it if you want). The original TEX file was made by Paulo Rezende, now back in Brazil (at Unicamp), and it was converted by Paulo Soares (working presently in Portugal), who I contacted at the time. He posted no objection of us replacing the file. Asking him was nice, but from a legal point of view, he can't sue anyone for replacing his file by something else :-) J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Markers in areas
They are not connected concepts, Mark. I originally put in the code for lineage pairs, and also started the implementation for markers. So I can assure you that they are completely unrelated. For what it's worth, subsequent contributors have significantly improved on marker support, so I am only commenting from the viewpoint of my knowledge of the spec. I made a few comments in my reply to Joerg. I have a degree in physics, and most of a Masters in physical oceanography. I see considerable mathematical anarchy in the XSL spec, some degree of mathematical naivete, and lots of confusion. My forte is not logic, based on my background, but even a physics guy can dissect the pseudo-logic in that spec. I think plenty of other people have also separated the wheat from the chaff as far as that document is concerned...I think we are due for a rewrite, with lots of the pretentious math excised, and replaced with plain language. Arved > -Original Message- > From: Mark C. Allman [mailto:[EMAIL PROTECTED]] > Sent: February 18, 2003 5:16 PM > To: [EMAIL PROTECTED] > Subject: RE: Markers in areas > > > ... but markers will continue to work as per the XSLFO spec, correct? > We depend on markers for dynamic page headings. > > -- Mark C. Allman > -- Allman Professional Consulting, Inc. > -- www.allmanpc.com, 617-947-4263 > > > -Original Message- > From: J.Pietschmann [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 18, 2003 4:09 PM > To: [EMAIL PROTECTED] > Subject: Re: Markers in areas > > Arved Sandstrom wrote: > > Joerg, you can freely get rid of that stuff. > > Great! > Anybody out there bothering to profile the new code? Two > objects less created per Area, this should be noticable! > > J.Pietschmann > > > - > 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: Markers in areas
... but markers will continue to work as per the XSLFO spec, correct? We depend on markers for dynamic page headings. -- Mark C. Allman -- Allman Professional Consulting, Inc. -- www.allmanpc.com, 617-947-4263 -Original Message- From: J.Pietschmann [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 18, 2003 4:09 PM To: [EMAIL PROTECTED] Subject: Re: Markers in areas Arved Sandstrom wrote: > Joerg, you can freely get rid of that stuff. Great! Anybody out there bothering to profile the new code? Two objects less created per Area, this should be noticable! J.Pietschmann - 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: Markers in areas
Arved Sandstrom wrote: Joerg, you can freely get rid of that stuff. Great! Anybody out there bothering to profile the new code? Two objects less created per Area, this should be noticable! J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Licence issues in hyphenation patterns
Christian Geisert wrote: And IMHO (and IANAL etc.) this is the crux as the Apache Software License does not forbid renamming the files. Yes, that's hairsplitting and comletly against common sense but remember we're talking about legal issues her. I meant the following LPPL condition: 3. You must not distribute the modified file with the filename of the original file. (from http://www.latex-project.org/lppl.txt) Because the FOP files end in .xml rather than .tex, we conform at least technically. The idea was probably to avoid the confusion of having several "hyphde.tex" files floating around, vaguely similar to the prohibition of using "Apache" for products derived from ASF code. A binary distribution is another matter because of the compiled *.hyph files, which are obviously derived. But again it should Hu? Above you said the XML files are also derived. What's the difference between source and binary distribution? The XML files (at least the file I examined) had a pointer to the original file, as required by LPPL 8(B). The binaries obviously don't have it, so we have to put this elsewhere preferably in the place where it's mentioned that certain compiled hyph files derived from LPPL'd files. I'm not sure whether our hyph "compilation" consitutes a mechanical transformation, which causes the result to be "another representation of the Original Work" so that it inherits the copyright and the license of the source, or whether the serialized class is a "Derived Work", where we could claim copyright and set license conditions. The LPPL'd hyphenation have to be checked thouroughly because of LPPL 1. Condition 2 does not apply. Condition 7 is fulfilled by keeping the file under LPPL. 3 is probably trivially ok as mentioned above. 4, 5 and 6 can be easily checked and corrected, and 8(B) should be easy too. I can look into it this weekend. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
ready to go again
OK, I am ready to jump in & do some work. Sorry for being out of action for so long. The threads that I would like to complete, or at least resolve, first, are: 1. Documentation. The main problem here is the web site generation, but it seemed to me that Peter and some others may have gotten that working. If so, is the readme doc up-to-date? (The last time I tried to run it, in December, the generation failed with errors). 2. Fonts. Jeremias & had some brief design conversations a few weeks ago. He argued for an interface, I argued for a concrete facade implementation. He is probably getting his doctrine from the "Design Patterns" book, and he is probably correct. Another principle taught in that book is that inheritance tends to be overrused, and that is specifically what I am trying to prevent with my approach. In my mind, there is tension between encapsulation and inheritance. So, if we can hide all of the implementation details behind the interface just as well as we can behind a facade, so that layout doesn't know or care what kind of font it is dealing with, then we are OK. Ideally, we want to do the same thing for the renderers, if possible. Victor Mote (mailto:[EMAIL PROTECTED]) 2025 Eddington Way Colorado Springs, Colorado 80916 Voice +1 (719) 622-0650 Fax +1 (720) 293-0044 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Hyphenation patterns included in fop-0.20.5rc2
Esteemed feathery FOPpers, BTW, congrats & stuff on the release! I just ran it, and it didn't give me an error! ;-) Would you let us know which hyphenation files are included with FOP 0.20.5rc2? I think that would be useful information to include in the fop-dev & fop-user mailing lists for archival/searching purposes, and the only reference to what is included is en_GB. It might also be useful to include in the reply, the status of other hyphenation patterns (and links if they exist). I checked out the current installation, and had a tough time finding info on Hyphenation. After doing a search on the fop-0.20.5rc2 directory, I found this file: fop-0.20.5rc2\examples\fo\basic\hyphen.fo Is that example the sum total of the hyphenation stuff in FOP? Or was everything removed (Christian indicated "removal of some hyphenation patterns")? If it's there, then I couldn't find it. If it's not, then the RelNotes should read "most" hyphenation patterns... Thanks for the great effort! It looks *great*! Web Maestro Clay Christian Geisert wrote: Hi all, the second Release Candidate for 0.20.5 is finally available at http://www.apache.org/dist/xml/fop for downloading and testing. (New download location - please use a mirror if possible) It is planed to make the actual release on on february the 28th if no serious bugs show up. The changes from the previous release candidate includes some bugfixes (marker handling, leader with page-citation, Jimi usage and more) but also the removal of some hyphenation patterns due to licensing reasons. Changes since 0.20.4 include: - Fixed link hotspot positioning - Fixed multi-threading issues - Added autoselecting portrait/landscape on PCL Renderer - Improved AWT Font-measuring/rendering - Perfomance tuning - Added support for CCITT Group 4 encoded TIFF files - Dynamic JAI support - Fixed problem with jpegs with icc profile and acrobat reader 5 - Added a fontBaseDir property - TXTRenderer output encoding - border-spacing support For details see CHANGES file: http://cvs.apache.org/viewcvs.cgi/xml-fop/CHANGES?rev=1.10.2.50 Please send feedback/bugreports to the mailing list or enter them in Bugzilla. Enjoy, Christian -- 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]
Re: [ANNOUNCEMENT] FOP 0.20.5 Release Candidate 2 available
At 09:08 AM 2/18/2003, you wrote: the second Release Candidate for 0.20.5 is finally available at http://www.apache.org/dist/xml/fop for downloading and testing. (New download location - please use a mirror if possible) Cheers, and congratulations all around. This was a bumpy one (especially for the drivers, I think) ' Best, -Ralph LaChance In theory, there is no difference between theory and practice, but in practice there is. (Jan L.A. van de Snepsheut (1953-1994), late of CalTech) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Licence issues in hyphenation patterns
>And, well, I hope our PetroBras friend changed enough of the >pt.xml to claim copyright, as he assigned it summarily to >the ASF... nice, but a real legal burden! I checked it in, but >now I think I should have asked for a paper first. I didn't modify the old pt.xml file, I wrote a new one entirely from scratch. If you diff the files you can see that very clearly. The old one didn't even take accented characters into consideration (he claimed so, but the patterns contained no accented characters), and produced a lot of errors. It also defined some words in the section which where hyphenated incorrectly. The original TEX file was made by Paulo Rezende, now back in Brazil (at Unicamp), and it was converted by Paulo Soares (working presently in Portugal), who I contacted at the time. He posted no objection of us replacing the file. (In fact, he doesn't use FOP at all and actually works in a rival project...) = Marcelo Jaccoud Amaral Petrobrás (http://www.petrobras.com.br) mailto:[EMAIL PROTECTED] = "A História é uma velhota que se repete sem cessar." Eça de Queiroz, in "Cartas de Inglaterra" - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[ANNOUNCEMENT] FOP 0.20.5 Release Candidate 2 available
Hi all, the second Release Candidate for 0.20.5 is finally available at http://www.apache.org/dist/xml/fop for downloading and testing. (New download location - please use a mirror if possible) It is planed to make the actual release on on february the 28th if no serious bugs show up. The changes from the previous release candidate includes some bugfixes (marker handling, leader with page-citation, Jimi usage and more) but also the removal of some hyphenation patterns due to licensing reasons. Changes since 0.20.4 include: - Fixed link hotspot positioning - Fixed multi-threading issues - Added autoselecting portrait/landscape on PCL Renderer - Improved AWT Font-measuring/rendering - Perfomance tuning - Added support for CCITT Group 4 encoded TIFF files - Dynamic JAI support - Fixed problem with jpegs with icc profile and acrobat reader 5 - Added a fontBaseDir property - TXTRenderer output encoding - border-spacing support For details see CHANGES file: http://cvs.apache.org/viewcvs.cgi/xml-fop/CHANGES?rev=1.10.2.50 Please send feedback/bugreports to the mailing list or enter them in Bugzilla. Enjoy, Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs tabs.xml
chrisg 2003/02/18 04:45:36 Modified:src/documentation/content/xdocs Tag: fop-0_20_2-maintain tabs.xml Log: forgot this one Revision ChangesPath No revision No revision 1.2.2.4 +8 -11 xml-fop/src/documentation/content/xdocs/tabs.xml Index: tabs.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/tabs.xml,v retrieving revision 1.2.2.3 retrieving revision 1.2.2.4 diff -u -r1.2.2.3 -r1.2.2.4 --- tabs.xml 18 Feb 2003 04:47:45 - 1.2.2.3 +++ tabs.xml 18 Feb 2003 12:45:35 - 1.2.2.4 @@ -2,14 +2,11 @@ http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/tab-cocoon-v10.dtd";> -http://www.w3.org/1999/xlink";> - - - - - - - + http://www.w3.org/1999/xlink";> + + + + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/resources/images EmbeddingExampleFO2PDF.png EmbeddingExampleFO2PDF.svg EmbeddingExampleObj2PDF.png EmbeddingExampleObj2PDF.svg EmbeddingExampleObj2XML.png EmbeddingExampleObj2XML.svg EmbeddingExampleXML2FO.png EmbeddingExampleXML2FO.svg EmbeddingExampleXML2PDF.png EmbeddingExampleXML2PDF.svg
chrisg 2003/02/18 04:27:35 Modified:.Tag: fop-0_20_2-maintain build.xml src/documentation/content/xdocs Tag: fop-0_20_2-maintain book.xml download.xml faq.xml involved.xml Added: src/documentation/content/xdocs Tag: fop-0_20_2-maintain logocontest.xml src/documentation/content/xdocs/fo Tag: fop-0_20_2-maintain align.fo align2.fo blocks.ent embed.fo fonts.fo size.fo src/documentation/resources/images Tag: fop-0_20_2-maintain EmbeddingExampleFO2PDF.png EmbeddingExampleFO2PDF.svg EmbeddingExampleObj2PDF.png EmbeddingExampleObj2PDF.svg EmbeddingExampleObj2XML.png EmbeddingExampleObj2XML.svg EmbeddingExampleXML2FO.png EmbeddingExampleXML2FO.svg EmbeddingExampleXML2PDF.png EmbeddingExampleXML2PDF.svg Log: added missing docs from head Revision ChangesPath No revision No revision 1.44.2.37 +1 -6 xml-fop/build.xml Index: build.xml === RCS file: /home/cvs/xml-fop/build.xml,v retrieving revision 1.44.2.36 retrieving revision 1.44.2.37 diff -u -r1.44.2.36 -r1.44.2.37 --- build.xml 18 Feb 2003 04:47:45 - 1.44.2.36 +++ build.xml 18 Feb 2003 12:27:34 - 1.44.2.37 @@ -112,11 +112,6 @@ - - - - - @@ -725,7 +720,7 @@ - + No revision No revision 1.7.2.4 +0 -2 xml-fop/src/documentation/content/xdocs/book.xml Index: book.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/book.xml,v retrieving revision 1.7.2.3 retrieving revision 1.7.2.4 diff -u -r1.7.2.3 -r1.7.2.4 --- book.xml 18 Feb 2003 04:47:45 - 1.7.2.3 +++ book.xml 18 Feb 2003 12:27:34 - 1.7.2.4 @@ -21,8 +21,6 @@ - - 1.3.2.4 +2 -2 xml-fop/src/documentation/content/xdocs/download.xml Index: download.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/download.xml,v retrieving revision 1.3.2.3 retrieving revision 1.3.2.4 diff -u -r1.3.2.3 -r1.3.2.4 --- download.xml 18 Feb 2003 04:47:45 - 1.3.2.3 +++ download.xml 18 Feb 2003 12:27:34 - 1.3.2.4 @@ -17,12 +17,12 @@ on AnonCVS in the http://xml.apache.org/cvs.html";>xml.apache.org documentation for details. Sometimes people have difficulties to access the cvs server; in this case you can download a snapshot from the cvs files http://xml.apache.org/from-cvs/xml-fop/";>here. - In both cases you have to build FOP yourself - see Compiling FOP for details. + In both cases you have to build FOP yourself - see Compiling Fop for details. Important: Currently, releases of FOP are coming out of the "fop-0_20_2-maintain" branch. The "MAIN" branch is currently - under development. See Development Docs + under development. See http://xml.apache.org/fop/dev/index.html";>Development Docs for more information. To run FOP from the command line, see Running FOP. 1.3.2.5 +1 -2 xml-fop/src/documentation/content/xdocs/faq.xml Index: faq.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/faq.xml,v retrieving revision 1.3.2.4 retrieving revision 1.3.2.5 diff -u -r1.3.2.4 -r1.3.2.5 --- faq.xml 18 Feb 2003 04:47:45 - 1.3.2.4 +++ faq.xml 18 Feb 2003 12:27:34 - 1.3.2.5 @@ -294,8 +294,7 @@ Reducing memory consumption in general and squishing bugs is an - ongoing effort, partially addressed in the redesign. + ongoing effort, partially addressed in the redesign. 1.2.2.4 +1 -1 xml-fop/src/documentation/content/xdocs/involved.xml Index: involved.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/involved.xml,v retrieving revision 1.2.2.3 retrieving revision 1.2.2.4 diff -u -r1.2.2.3 -r1.2.2.4 --- involved.xml 18 Feb 2003 04:47:45 - 1.2.2.3 +++ involved.xml 18 Feb 20
RE: Adding a .png Image
Hi Venkata, are you receiving any error messages? Like "Jimi image library not available"? If so you need to download the JIMI library from Sun Microsystems at http://java.sun.com/products/jimi/ and make sure the the classes are picked up. -Original Message- Hello , I want to insert a .png image in table but it seems .png is not supported. can anyone suggest me a solution where I can achieve this. Thanks in Advance, Venkata Suresh. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Adding a .png Image
Hello , I want to insert a .png image in table but it seems .png is not supported. can anyone suggest me a solution where I can achieve this. Thanks in Advance, Venkata Suresh. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Can't bind page number into a variable
Hi Simon, I'm afraid but there is no way to know on which page you are. Is there a reason why you can't put the page number into a static area? If you can then the following snippets might help: 1. Define your pages (left / right) 2. Assign them to odd / even page numbers 3. Use the page sequence and add layout specific to even / odd pages ... BTW: Please use fop-users list for questions like this in future. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, February 17, 2003 9:51 PM To: [EMAIL PROTECTED] Subject: Can't bind page number into a variable Hi, I would like to put specific attributes on odd or even pages, so I began by looking for a way to check the context pages but I did'nt find anything. So I wanted to bind the into a variable in order to make some test on it when I want to add specific parameters to my tags. start end But it looks like being impossible to bind the into a variable or param (I tried to write my variable in a block but it looks like being setted to "" by the fo:page-number tag). Is here a reason for my variable to be null ? And is there a way to detect the context where I am currently in while writing in a non-static content ? I also tried to make a template with a page_number param but it doesn't work either... Here are some examples of my pdf outputs : http://www.tatouage.fr/temp/ap_skin_example.pdf (here I want to align my titles at the start or the end of the block depending of the odd or even condition, I am in a non-static context) http://www.tatouage.fr/temp/cd_skin_example.pdf (It's the same with this skin but it will be easier for me because every objects have statical position on the page = I have one odd and one even page for each XML tag, so I'll be able to manage the whole page breaking in XSLT) Sorry for disturbing you developpers with my little problem, but it makes me so nervous ... :/ Thanks for your work on this API. Simon OUALID - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
