Re: Using Just the Font Metrics Stuff From FOP
The OpenType reader code is in TTFReader. OpenType is an evolution of TrueType. Maybe you could try to use the TTFReader from 0.20.5. The HEAD TTFReader should be at least equal in functionality but I can't be sure we got all fixes for 0.20.5 into HEAD already. Good luck! On 07.01.2004 02:12:38 Eliot Kimber wrote: I tried the TTFReader on my OpenType font and it died in ReadGlyf() :-( I see in a message from Victor Mote from July of 2003 that he had an OpenType reader working but not committed. Is the OpenType reader code available or has the OpenType support been pushed to somewhere else? Jeremias Maerki
Re: Is there going to be another release of the 0.20 branch?
J.Pietschmann wrote: Well, we could release the current CVS as 0.20.5.1. The table memory fix is probably important to many users. THere is a slo a minor fix concerning leader expansion there. Okay, but you said yourself that the adjustments you made to tables has probably broken some other things, so we would need to go through a RC, and bug fix cycle. Chris
Re: Is there going to be another release of the 0.20 branch?
I don't want to start a war here, but if ( that's a big if) we're going to go through the hassle of doing an RC, does it make sense to insert any new functionality into FOP, like TIF output? I understand Oleg Tkachenko's work for TIF is complete (or nearly complete), but (like many PATCHes) was excluded due to code-freeze. My company just implemented some systems which use TIF output, and we have to go through hoops (XML/XSL-FO=PostScript and then from Postscript=TIF via GhostScript). It works but is clunky. Since it works, this isn't a make-or-break for me, but is more of a would be nice... I don't know what else there is out there in the way of completed PATCHes for highly desirable benefits that are ready (or almost ready) for prime time. There could certainly be other items we're missing due to the self-imposed code freeze. For me the issue is not so much what other things can we shoe-horn into FOP. It's more of an issue with what features can be added to FOP to make it even more desirable and get more users (and developers) on board. Web Maestro Clay On Jan 7, 2004, at 12:42 AM, Chris Bowditch wrote: J.Pietschmann wrote: Well, we could release the current CVS as 0.20.5.1. The table memory fix is probably important to many users. THere is a slo a minor fix concerning leader expansion there. Okay, but you said yourself that the adjustments you made to tables has probably broken some other things, so we would need to go through a RC, and bug fix cycle. Chris
Re: Using Just the Font Metrics Stuff From FOP
Jeremias Maerki wrote: The OpenType reader code is in TTFReader. OpenType is an evolution of TrueType. Maybe you could try to use the TTFReader from 0.20.5. The HEAD TTFReader should be at least equal in functionality but I can't be sure we got all fixes for 0.20.5 into HEAD already. Cool--what tag do I use to checkout the 0.20.5? I'm not sure I completely understood what the FOP CVS information was telling me. Thanks, Eliot -- W. Eliot Kimber Professional Services Innodata Isogen 9030 Research Blvd, #410 Austin, TX 78758 (512) 372-8122 [EMAIL PROTECTED] www.innodata-isogen.com
Re: Is there going to be another release of the 0.20 branch?
Clay Leeds wrote: I don't want to start a war here, but if ( that's a big if) we're going to go through the hassle of doing an RC, does it make sense to insert any new functionality into FOP, like TIF output? I understand Oleg Tkachenko's work for TIF is complete (or nearly complete), but (like many PATCHes) was excluded due to code-freeze. My company just implemented some systems which use TIF output, and we have to go through hoops (XML/XSL-FO=PostScript and then from Postscript=TIF via GhostScript). It works but is clunky. Since it works, this isn't a make-or-break for me, but is more of a would be nice... I understand the desire to add new features like the Tif generator into the maintenance code. However, doing so would mean effort is distracted away from HEAD development. The sooner we can do a release from HEAD then the sooner FOP gets out of the twilight zone. Chris
Re: Using Just the Font Metrics Stuff From FOP
Eliot Kimber wrote: snip/ Cool--what tag do I use to checkout the 0.20.5? I'm not sure I completely understood what the FOP CVS information was telling me. The tag you need is: fop-0_20_2-maintain Chris
Re: Is there going to be another release of the 0.20 branch?
On Jan 7, 2004, at 7:46 AM, Chris Bowditch wrote: Clay Leeds wrote: I don't want to start a war here, but if ( that's a big if) we're going to go through the hassle of doing an RC, does it make sense to insert any new functionality into FOP, like TIF output? I understand Oleg Tkachenko's work for TIF is complete (or nearly complete), but (like many PATCHes) was excluded due to code-freeze. My company just implemented some systems which use TIF output, and we have to go through hoops (XML/XSL-FO=PostScript and then from Postscript=TIF via GhostScript). It works but is clunky. Since it works, this isn't a make-or-break for me, but is more of a would be nice... I understand the desire to add new features like the Tif generator into the maintenance code. However, doing so would mean effort is distracted away from HEAD development. The sooner we can do a release from HEAD then the sooner FOP gets out of the twilight zone. Chris Thanks for the respectful response. I'm aware that HEAD release is adversely affected by MAINTENANCE work (hence the I don't want to start a ware here, but... :-)), however, I posted this for a few of reasons: 1) fop-dev team might discuss this in light of the possibility of another release and/or RC; 2) aside from the table/memory issues, I wonder what other changes would be included; 3) what PATCHes to fop-0_20_2-maintain were close to completion prior to code-freeze? Since I'm starting to get up to speed w CVS, I guess I can go and look myself for 2 3. As for #3, I guess part of that would hinge on whether the PATCH developer currently has the time to devote to adjusting the code for 0.20.51 (or whatever it'll be called). In the case of TIF output, I believe the developer wrote it for 0.20.3. Then again, even the prospect of reading and/or responding to this thread takes the good fop-dev committing team away from HEAD development, so this'll be my last post on the subject unless further discussion is warranted. Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
RE: Is there going to be another release of the 0.20 branch?
-Original Message- From: Chris Bowditch [mailto:[EMAIL PROTECTED] snip / I understand the desire to add new features like the Tif generator into the maintenance code. However, doing so would mean effort is distracted away from HEAD development. The sooner we can do a release from HEAD then the sooner FOP gets out of the twilight zone. I tend to agree with Chris here. Maybe the current CVS code for maintenance could be just built and added to the distributions download page. Then we can put a bit of explanation on the web page for those interested ... but I'd keep the fuss rather minimal for the moment (--but maybe nothing but my lazy alter ego speaking here ;) ) There may be quite some work left on HEAD, but in the last few weeks, I'm getting the impression that things are actually moving forward (cfr. Finn's and Simon's numerous patch proposals to Layout and Properties) Apart from a committer deciding to leave (or, at least, take a step back from) FOP, we have had little or no drawbacks in dev lately, so my guess would be that all is looking quite good (for now) If a vote were being called? Hmmm... tough one... I guess one thing we mustn't forget is that --how long exactly has it been since there was talk about 'the redesigned FOP'? If judged from that side, to release another 'minor update' would be a mistake IMHO. OTOH I have currently too little info (and too much enthousiasm) to make a clear, educated guess about the time it will take to get the current HEAD ready for average use... I would refrain: 0 Clay Leeds wrote: Then again, even the prospect of reading and/or responding to this thread takes the good fop-dev committing team away from HEAD development, so this'll be my last post on the subject unless further discussion is warranted. Maestro, Jus' remember: all recipients who do not want to read, have the choice to ignore your message upon receipt. Good ideas, fella, good ideas are *always* welcome :) Cheers, Andreas
RE: Help with the sample FopServlet
-Original Message- From: John Austin [mailto:[EMAIL PROTECTED] snip / I forget some of the servlet details too. I was a bit surprised by the assertion that placing readme.fo in $TOMCAT_ROOT/bin worked. Yeah, puzzled me a bit as well in the OP. So there was my calculated guess. snip / I meant to post that to fop-dev but the 'reply-to' address pointed to you. I see... Well, no harm done in any case. Better now? Cheers, Andreas
Attribute processing order (was: Re: [Bug 25803] - [PATCH] PropertyList: Fixes to convertAttributeToProperty and findBaseProperty)
On Thu, Jan 01, 2004 at 12:20:09AM -, [EMAIL PROTECTED] wrote: --- Additional Comments From [EMAIL PROTECTED] 2004-01-01 00:20 --- Alt-Design addresses this problem by the simple expedient of processing properties in integer property number order. In main that is not possible. When a compound attribute is encountered, a compound property is made in which the components are set to default values. Then the specified component is set to the specified value. After this it cannot be told which components were specified by the user and which were defaulted by the program. Therefore, before dealing with the compound attribute, the base attribute should be processed if that is specified as well. This would be different if the compound property would not be filled with default components, but with null components. Regards, Simon -- Simon Pepping email: [EMAIL PROTECTED] home page: http://www.leverkruid.nl public key: http://www.leverkruid.nl/personal/sp.asc fingerprint: E3BF 7295 9AA8 8B8A C01A 219D FAAC 088C 6B28 F549
Re: Is there going to be another release of the 0.20 branch?
On Jan 7, 2004, at 12:07 PM, J.Pietschmann wrote: It works for me for generating PDF for quite some time. I get NPE when reloading a FO source in the AWT appilcation, but this maz have other reasons, I didn't try to track it down. As long as I can remember I got NPE when clicking the [Reload] button in AWT while running FOP (w fop-0.20.5 fop-0.20.4). I just took it as fact that this was something we're not supposed to do. Web Maestro Clay
cvs commit: xml-fop/src/java/org/apache/fop/fo Property.java PropertyList.java
gmazza 2004/01/07 13:10:39
Modified:src/codegen properties.xsl
src/java/org/apache/fop/datatypes CompoundDatatype.java
CondLength.java Keep.java LengthPair.java
src/java/org/apache/fop/fo Property.java PropertyList.java
Log:
Last of string-int conversions (more structural improvements still can be
done in PropertyList from Finn's patch, however). Made Constants values
inherent to CompoundDatatype class.
Revision ChangesPath
1.28 +2 -3 xml-fop/src/codegen/properties.xsl
Index: properties.xsl
===
RCS file: /home/cvs/xml-fop/src/codegen/properties.xsl,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- properties.xsl6 Jan 2004 00:49:40 - 1.27
+++ properties.xsl7 Jan 2004 21:10:36 - 1.28
@@ -576,8 +576,7 @@
return baseProp;
}
-public Property getSubpropValue(Property baseProp, String subpropName) {
-int subpropId =
org.apache.fop.fo.properties.FOPropertyMapping.getSubPropertyId(subpropName);
+public Property getSubpropValue(Property baseProp, int subpropId) {
/xsl:text
xsl:value-of select=datatype/
xsl:text val = baseProp.get/xsl:text
1.3 +2 -1 xml-fop/src/java/org/apache/fop/datatypes/CompoundDatatype.java
Index: CompoundDatatype.java
===
RCS file: /home/cvs/xml-fop/src/java/org/apache/fop/datatypes/CompoundDatatype.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- CompoundDatatype.java 6 Jan 2004 00:49:40 - 1.2
+++ CompoundDatatype.java 7 Jan 2004 21:10:36 - 1.3
@@ -51,11 +51,12 @@
package org.apache.fop.datatypes;
import org.apache.fop.fo.Property;
+import org.apache.fop.fo.Constants;
/**
* This interface is used as a base for compound datatypes.
*/
-public interface CompoundDatatype {
+public interface CompoundDatatype extends Constants {
/**
* Sets a component of the compound datatype.
1.5 +4 -4 xml-fop/src/java/org/apache/fop/datatypes/CondLength.java
Index: CondLength.java
===
RCS file: /home/cvs/xml-fop/src/java/org/apache/fop/datatypes/CondLength.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- CondLength.java 6 Jan 2004 00:49:40 - 1.4
+++ CondLength.java 7 Jan 2004 21:10:36 - 1.5
@@ -67,9 +67,9 @@
*/
public void setComponent(int cmpId, Property cmpnValue,
boolean bIsDefault) {
-if (cmpId == Constants.CP_LENGTH) {
+if (cmpId == CP_LENGTH) {
length = cmpnValue;
-} else if (cmpId == Constants.CP_CONDITIONALITY) {
+} else if (cmpId == CP_CONDITIONALITY) {
conditionality = cmpnValue;
}
}
@@ -78,9 +78,9 @@
* @see org.apache.fop.datatypes.CompoundDatatype#getComponent(int)
*/
public Property getComponent(int cmpId) {
-if (cmpId == Constants.CP_LENGTH) {
+if (cmpId == CP_LENGTH) {
return length;
-} else if (cmpId == Constants.CP_CONDITIONALITY) {
+} else if (cmpId == CP_CONDITIONALITY) {
return conditionality;
} else {
return null;
1.6 +6 -6 xml-fop/src/java/org/apache/fop/datatypes/Keep.java
Index: Keep.java
===
RCS file: /home/cvs/xml-fop/src/java/org/apache/fop/datatypes/Keep.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- Keep.java 6 Jan 2004 00:49:40 - 1.5
+++ Keep.java 7 Jan 2004 21:10:36 - 1.6
@@ -73,11 +73,11 @@
*/
public void setComponent(int cmpId, Property cmpnValue,
boolean bIsDefault) {
-if (cmpId == Constants.CP_WITHIN_LINE) {
+if (cmpId == CP_WITHIN_LINE) {
setWithinLine(cmpnValue, bIsDefault);
-} else if (cmpId == Constants.CP_WITHIN_COLUMN) {
+} else if (cmpId == CP_WITHIN_COLUMN) {
setWithinColumn(cmpnValue, bIsDefault);
-} else if (cmpId == Constants.CP_WITHIN_PAGE) {
+} else if (cmpId == CP_WITHIN_PAGE) {
setWithinPage(cmpnValue, bIsDefault);
}
}
@@ -86,11 +86,11 @@
* @see org.apache.fop.datatypes.CompoundDatatype#getComponent(int)
*/
public Property getComponent(int cmpId) {
-if (cmpId == Constants.CP_WITHIN_LINE) {
+if (cmpId == CP_WITHIN_LINE) {
return getWithinLine();
-
cvs commit: xml-fop/src/java/org/apache/fop/datatypes LengthRange.java Space.java
gmazza 2004/01/07 13:28:42
Modified:src/java/org/apache/fop/datatypes LengthRange.java
Space.java
Log:
Constants simplifications in LengthRange and Space.java.
Revision ChangesPath
1.6 +6 -7 xml-fop/src/java/org/apache/fop/datatypes/LengthRange.java
Index: LengthRange.java
===
RCS file: /home/cvs/xml-fop/src/java/org/apache/fop/datatypes/LengthRange.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- LengthRange.java 6 Jan 2004 00:49:40 - 1.5
+++ LengthRange.java 7 Jan 2004 21:28:42 - 1.6
@@ -51,7 +51,6 @@
package org.apache.fop.datatypes;
import org.apache.fop.fo.Property;
-import org.apache.fop.fo.Constants;
/**
* A progression-dimension quantity.
@@ -74,11 +73,11 @@
*/
public void setComponent(int cmpId, Property cmpnValue,
boolean bIsDefault) {
-if (cmpId == Constants.CP_MINIMUM) {
+if (cmpId == CP_MINIMUM) {
setMinimum(cmpnValue, bIsDefault);
-} else if (cmpId == Constants.CP_OPTIMUM) {
+} else if (cmpId == CP_OPTIMUM) {
setOptimum(cmpnValue, bIsDefault);
-} else if (cmpId == Constants.CP_MAXIMUM) {
+} else if (cmpId == CP_MAXIMUM) {
setMaximum(cmpnValue, bIsDefault);
}
}
@@ -87,11 +86,11 @@
* @see org.apache.fop.datatypes.CompoundDatatype#getComponent(int)
*/
public Property getComponent(int cmpId) {
-if (cmpId == Constants.CP_MINIMUM) {
+if (cmpId == CP_MINIMUM) {
return getMinimum();
-} else if (cmpId == Constants.CP_OPTIMUM) {
+} else if (cmpId == CP_OPTIMUM) {
return getOptimum();
-} else if (cmpId == Constants.CP_MAXIMUM) {
+} else if (cmpId == CP_MAXIMUM) {
return getMaximum();
} else {
return null;// SHOULDN'T HAPPEN
1.5 +4 -5 xml-fop/src/java/org/apache/fop/datatypes/Space.java
Index: Space.java
===
RCS file: /home/cvs/xml-fop/src/java/org/apache/fop/datatypes/Space.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- Space.java6 Jan 2004 00:49:40 - 1.4
+++ Space.java7 Jan 2004 21:28:42 - 1.5
@@ -51,7 +51,6 @@
package org.apache.fop.datatypes;
import org.apache.fop.fo.Property;
-import org.apache.fop.fo.Constants;
/**
* a space quantity in XSL (space-before, space-after)
@@ -66,9 +65,9 @@
*/
public void setComponent(int cmpId, Property cmpnValue,
boolean bIsDefault) {
-if (cmpId == Constants.CP_PRECEDENCE) {
+if (cmpId == CP_PRECEDENCE) {
setPrecedence(cmpnValue, bIsDefault);
-} else if (cmpId == Constants.CP_CONDITIONALITY) {
+} else if (cmpId == CP_CONDITIONALITY) {
setConditionality(cmpnValue, bIsDefault);
} else {
super.setComponent(cmpId, cmpnValue, bIsDefault);
@@ -79,9 +78,9 @@
* @see org.apache.fop.datatypes.CompoundDatatype#getComponent(int)
*/
public Property getComponent(int cmpId) {
-if (cmpId == Constants.CP_PRECEDENCE) {
+if (cmpId == CP_PRECEDENCE) {
return getPrecedence();
-} else if (cmpId == Constants.CP_CONDITIONALITY) {
+} else if (cmpId == CP_CONDITIONALITY) {
return getConditionality();
} else {
return super.getComponent(cmpId);
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/java/org/apache/fop/fo Property.java
gmazza 2004/01/07 14:25:43
Modified:src/codegen properties.xsl
src/java/org/apache/fop/fo Property.java
Log:
More String-int conversions.
Revision ChangesPath
1.29 +19 -13xml-fop/src/codegen/properties.xsl
Index: properties.xsl
===
RCS file: /home/cvs/xml-fop/src/codegen/properties.xsl,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- properties.xsl7 Jan 2004 21:10:36 - 1.28
+++ properties.xsl7 Jan 2004 22:25:42 - 1.29
@@ -523,10 +523,12 @@
super(propId);/xsl:text
xsl:if test=compound
xsl:text
-m_shorthandMaker= getSubpropMaker(/xsl:text
-xsl:value-of select=
-'compound/[EMAIL PROTECTED]true]/name'/
-xsl:text);/xsl:text
+m_shorthandMaker= getSubpropMaker(Constants.CP_/xsl:text
+xsl:call-template name=makeEnumConstant
+ xsl:with-param name=propstr select=
+ 'compound/[EMAIL PROTECTED]true]/name'/
+/xsl:call-template
+xsl:text);/xsl:text
/xsl:if
xsl:text
}
@@ -544,7 +546,7 @@
return true;
}
-protected Property.Maker getSubpropMaker(String subprop) {/xsl:text
+protected Property.Maker getSubpropMaker(int subpropId) {/xsl:text
xsl:for-each select=compound/subproperty
xsl:variable name=spname
xsl:call-template name=makeClassName
@@ -552,15 +554,17 @@
/xsl:call-template
/xsl:variable
xsl:text
-if (subprop.equals(/xsl:text
- xsl:value-of select='name'/
- xsl:text))
+if (subpropId == Constants.CP_/xsl:text
+ xsl:call-template name=makeEnumConstant
+xsl:with-param name=propstr select=name/
+ /xsl:call-template
+ xsl:text)
return s_/xsl:text
xsl:value-of select=$spname/
xsl:textMaker;/xsl:text
/xsl:for-each
xsl:text
-return super.getSubpropMaker(subprop);
+return super.getSubpropMaker(subpropId);
}
protected Property setSubprop(Property baseProp, int subpropId,
@@ -624,9 +628,11 @@
// set default for subprop /xsl:text
xsl:value-of select=./
xsl:text
- subProp = getSubpropMaker(/xsl:text
-xsl:value-of select='.'/
-xsl:text).make(pList, getDefaultFor/xsl:text
+ subProp = getSubpropMaker(Constants.CP_/xsl:text
+xsl:call-template name=makeEnumConstant
+ xsl:with-param name=propstr select=./
+/xsl:call-template
+xsl:text).make(pList, getDefaultFor/xsl:text
xsl:value-of select='$spname'/
xsl:text(), fo);
p.setComponent(Constants.CP_/xsl:text
1.12 +5 -5 xml-fop/src/java/org/apache/fop/fo/Property.java
Index: Property.java
===
RCS file: /home/cvs/xml-fop/src/java/org/apache/fop/fo/Property.java,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- Property.java 7 Jan 2004 21:10:38 - 1.11
+++ Property.java 7 Jan 2004 22:25:43 - 1.12
@@ -141,12 +141,12 @@
* of compound property types, such as space.
* Overridden by property maker subclasses which handle
* compound properties.
- * @param subprop The name of the component for which a Maker is to
- * returned, for example optimum, if the FO attribute is
+ * @param subprop The Constants ID of the component for which a Maker is to
+ * returned, for example CP_OPTIMUM, if the FO attribute is
* space.optimum='10pt'.
* @return the Maker object specified
*/
-protected Maker getSubpropMaker(String subprop) {
+protected Maker getSubpropMaker(int subpropId) {
return null;
}
@@ -188,11 +188,11 @@
if (baseProp == null) {
baseProp = makeCompound(propertyList, fo);
}
-Maker spMaker = getSubpropMaker(partName);
+int partId = FOPropertyMapping.getSubPropertyId(partName);
+Maker spMaker = getSubpropMaker(partId);
if (spMaker != null) {
Property p = spMaker.make(propertyList, value, fo);
if (p != null) {
-int partId = FOPropertyMapping.getSubPropertyId(partName);
return setSubprop(baseProp, partId, p);
}
} else {
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
cvs commit: xml-fop/src/java/org/apache/fop/fo Property.java PropertyList.java
gmazza 2004/01/07 14:50:51
Modified:src/java/org/apache/fop/fo Property.java PropertyList.java
Log:
More String-int conversion.
Revision ChangesPath
1.13 +7 -5 xml-fop/src/java/org/apache/fop/fo/Property.java
Index: Property.java
===
RCS file: /home/cvs/xml-fop/src/java/org/apache/fop/fo/Property.java,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- Property.java 7 Jan 2004 22:25:43 - 1.12
+++ Property.java 7 Jan 2004 22:50:51 - 1.13
@@ -174,7 +174,8 @@
* value is already partially initialized, this method will modify it.
* @param baseProp The Property object representing the compound property,
* for example: SpaceProperty.
- * @param partName The name of the component whose value is specified.
+ * @param subpropId The Constants ID of the subproperty (component)
+ *whose value is specified.
* @param propertyList The propertyList being built.
* @param fo The FO whose properties are being set.
* @param value the value of the
@@ -182,18 +183,19 @@
* the new subproperty added
* @throws FOPException for invalid or inconsistent FO input
*/
-public Property make(Property baseProp, String partName,
+public Property make(Property baseProp, int subpropId,
PropertyList propertyList, String value,
FObj fo) throws FOPException {
if (baseProp == null) {
baseProp = makeCompound(propertyList, fo);
}
-int partId = FOPropertyMapping.getSubPropertyId(partName);
-Maker spMaker = getSubpropMaker(partId);
+
+Maker spMaker = getSubpropMaker(subpropId);
+
if (spMaker != null) {
Property p = spMaker.make(propertyList, value, fo);
if (p != null) {
-return setSubprop(baseProp, partId, p);
+return setSubprop(baseProp, subpropId, p);
}
} else {
//getLogger().error(compound property component
1.23 +2 -1 xml-fop/src/java/org/apache/fop/fo/PropertyList.java
Index: PropertyList.java
===
RCS file: /home/cvs/xml-fop/src/java/org/apache/fop/fo/PropertyList.java,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- PropertyList.java 7 Jan 2004 21:10:38 - 1.22
+++ PropertyList.java 7 Jan 2004 22:50:51 - 1.23
@@ -500,7 +500,8 @@
} else { // e.g. leader-length.maximum
Property baseProperty = findBaseProperty(attributes,
parentFO, basePropertyName, propertyMaker);
-prop = propertyMaker.make(baseProperty, subPropertyName,
+int subpropId = FOPropertyMapping.getSubPropertyId(subPropertyName);
+prop = propertyMaker.make(baseProperty, subpropId,
this, attributeValue, parentFO);
}
if (prop != null) {
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Chris Bowditch for Committer
Jeremias Maerki wrote: In recognition for his contributions to this project I'd like to propose Chris Bowditch as a FOP committer. He's active on both dev and user mailing lists for at least 18 months now. He's actively helping out on the user mailing list and shows interest in FOP development. Provided he accepts the nomination, I'd like to have him on the boat. +1 from me. +1 Christian
Re: [VOTE] Clay Leeds for committer
Jeremias Maerki wrote: In recognition for his contributions to this project I'd like to propose Web Maestro Clay Leeds as a FOP committer. He's active on both dev and user mailing lists for at least 1 year now. He's actively helping out on the user mailing list and as our favourite nit-picker :-) he was instrumental in improving our website. Provided he accepts the nomination, I'd like to have him on the boat. +1 from me. +1 Christian
Re: [VOTE] Andreas L. Delmelle for committer
Jeremias Maerki wrote: In recognition for his contributions to this project I'd like to propose Andreas L. Delmelle as a FOP committer. He's active on both dev and user mailing lists for over 6 months now. He's actively helping out on the user mailing list and shows interest in FOP development. Provided he accepts the nomination, I'd like to have him on the boat. +1 from me. +1 Christian
Re: Dropping support for 1.3 (was Re: PropertySets)
J.Pietschmann wrote: [..] Acutually I doubt FOP 0.20.5 will run completely in an 1.2 environment. The binary is compiled with 1.4.1, and I vaguely remember compiling No, with 1.3 problems already for 0.20.4 on 1.2. See http://marc.theaimsgroup.com/?l=fop-devm=102372166019810w=2 Christian
Re: Dropping support for 1.3 (was Re: PropertySets)
J.Pietschmann wrote: Chris Bowditch wrote: The main thing to bear in mind is that a few platforms dont support the later versions of Java. This will mean excluding those users from deploying FOP on their production servers and mainframes. Well. Java 1.4 has some added goodies, in particular nestable exceptions which will make problem tracking much easier, the BIDI support, other AWT fixes and extensions and JCE by default (people will still have to get a RC4 provider though :-/). And 1.4 has java.util.logging and java.util.prefs. -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
Re: Attribute processing order
Simon Pepping wrote: On Thu, Jan 01, 2004 at 12:20:09AM -, [EMAIL PROTECTED] wrote: --- Additional Comments From [EMAIL PROTECTED] 2004-01-01 00:20 --- Alt-Design addresses this problem by the simple expedient of processing properties in integer property number order. In main that is not possible. When a compound attribute is encountered, a compound property is made in which the components are set to default values. Then the specified component is set to the specified value. After this it cannot be told which components were specified by the user and which were defaulted by the program. Therefore, before dealing with the compound attribute, the base attribute should be processed if that is specified as well. This would be different if the compound property would not be filled with default components, but with null components. That's why a flat property space is not only feasible, but desirable. Compound properties are an unnecessary complication. Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
