Chris Bowditch has been voted in as new FOP committer. Please create a
new account for him.
+1: 6
+0: 0
-1: 0
Vote:
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]by=threadfrom=572506
Full name: Chris Bowditch
Preferred account name: cbowditch
eMail-address: [EMAIL
Andreas L. Delmelle has been voted in as new FOP committer. Please create a
new account for him.
+1: 5
+0: 0
-1: 0
(Note: There was a -1 that was later changed to a +1 with no -1s
remaining.)
Vote:
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]by=threadfrom=572508
Full name:
Account requests sent. The accounts will be activated as soon as the
CLAs arrive.
andreas seems to be taken as username so I took the second choice
(http://www.apache.org/~jim/committers.html).
Finn, Chris and Andreas, welcome aboard! I'm glad to see FOP getting
some speed again.
Jeremias
[Glen in bugzilla]
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25480
I'm now looking at the changes to PropertySets.java (already applied) and
PropertyList.java (only partly so) and have a few questions:
1.) For the new PropertyList constructor (in the patch), you appear to be
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=25480.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi,
Can't you use multiple page-sequences instead of just creating one sequence
'interrupted' by the 'ctrlPage' template?
but How?
this template is more difficult since it is used in with a more
complicated XML like groupproduct/.../group..., the way that I
sent is for brevety to discover
pbwest 2004/01/10 08:33:03
Added: .Tag: FOP_0-20-0_Alt-Design fop.bat
Log:
Adding execution support for WIndows from HEAD
Revision ChangesPath
No revision
No revision
1.3.2.2 +19 -1 xml-fop/fop.bat
pherweg 2004/01/10 11:43:58
Modified:src/java/org/apache/fop/fo FOInputHandler.java
FOTreeHandler.java
src/java/org/apache/fop/render/mif MIFHandler.java
src/java/org/apache/fop/render/rtf RTFHandler.java
gmazza 2004/01/10 12:40:07
Modified:src/codegen properties.xsl
src/java/org/apache/fop/datatypes
ToBeImplementedProperty.java
src/java/org/apache/fop/fo Property.java PropertySets.java
Log:
switch from Property.getPropName() to
Hi,
The code that I checked out this evening from CVS HEAD generates
compile errors, for example,
[javac]
/fsd/source/xml-fop/build/gensrc/org/apache/fop/fo/properties/BorderBottomStyleMaker.java:21:
cannot resolve symbol
[javac] symbol : variable PR_BORDER_AFTER_STYLE
[javac]
--- Finn Bock [EMAIL PROTECTED] wrote:
1.) For the new PropertyList constructor (in the
patch), you appear to be
duplicating the element ID argument, once as el,
the other time
as elementId--just to confirm, they are
referring to the same thing (and
hence one of them can be removed)?
--- Simon Pepping [EMAIL PROTECTED] wrote:
The cause is that the import section is not
sufficient:
package org.apache.fop.fo.properties;
import org.apache.fop.fo.*;
import org.apache.fop.apps.FOPException;
With these import statements the compiler applies
interface
--- Glen Mazza [EMAIL PROTECTED] wrote:
Yes, but the Eclipse warnings of unneeded imports
drives Peter West and a few others crazy. If the
above does not work, our only other solution would
be
a fully qualified import statement.
oops...I mean fully qualifying the Constants
variables.
[Glen Mazza]
... what's your opinion on switching to FO
Constants at this time? They probably will not give
us the rate of return that property constants have;
but there may be future indexing or processing
advantages with them. I'm not strong one way or the
other on them.
Since then, you have
14 matches
Mail list logo