Re: Interaction between force-page-count and initial-page-number

2004-02-09 Thread Chris Bowditch
Peter B. West wrote: snip/ The Rec says of force-page-number:auto, 'If there is no next page-sequence or if the value of its initial-page-number is auto do not force any page.' Should that read, '...the value of its initial-page-number is auto, auto-even or auto-odd...'? If not, some

Re: Contributions from competing products (was: Just a small question...)

2004-02-09 Thread Clay Leeds
Thanks for the kind comments, Glen. I look forward to discussing the topic of how to deal with contributions made by developers of competing products, and more importantly, the fruition of a plan or protocol to help guide us. Web Maestro Clay On Feb 6, 2004, at 3:46 PM, Glen Mazza wrote: ---

Re: FOP components

2004-02-09 Thread Clay Leeds
On Feb 8, 2004, at 3:37 AM, J.Pietschmann wrote: If we are involved in such considerations, we need to decide how we propose to support our 1.3 user base. The most recent discussions showed that a number of users face steep costs to upgrade to 1.4. As for the 1.4 discussion: The jakarta commons

Re: FOP components

2004-02-09 Thread Chris Bowditch
Clay Leeds wrote: On Feb 8, 2004, at 3:37 AM, J.Pietschmann wrote: snip/ I had a similar thought process (0_20_2-maintain for pre-1.4 users--if it works, don't fix it?). As for 1.0 (forgive my playing the devil's advocate here), why stop at 1.4? Assuming Java 1.5 will be released by the time

RE: FOP components

2004-02-09 Thread Andreas L. Delmelle
-Original Message- From: Clay Leeds [mailto:[EMAIL PROTECTED] snip / I had a similar thought process (0_20_2-maintain for pre-1.4 users--if it works, don't fix it?). As for 1.0 (forgive my playing the devil's advocate here), why stop at 1.4? Assuming Java 1.5 will be released by the

Re: JUnit test failure

2004-02-09 Thread Christian Geisert
J.Pietschmann wrote: Hi all, I get a nice Junit failure: Testcase: testFO2PDFWithDOM took 0.23 sec Caused an ERROR [..] This seems to have something to do mixing Jars form the JDK and fop/lib. Does anybody have an idea how this can be avoided? I had a similar problem with JUnit/Log4J some

Re: Interaction between force-page-count and initial-page-number

2004-02-09 Thread Peter B. West
Chris, Comments below. Chris Bowditch wrote: Peter B. West wrote: snip/ The Rec says of force-page-number:auto, 'If there is no next page-sequence or if the value of its initial-page-number is auto do not force any page.' Should that read, '...the value of its initial-page-number is auto,

PMC representation change, still ot ack'ed

2004-02-09 Thread Jeremias Maerki
I've just noticed that Joerg still hasn't been formally voted in in the XML PMC as a replacement for Peter. Since this was more than 2 months ago I wanted to check if this is still ok. I'll start the vote in the XML PMC on Wednesday if there are no objections until then. Jeremias Maerki

Re: FOP components (and JDK 1.4 requirement)

2004-02-09 Thread Jeremias Maerki
I'm pleasantly surprised by your proposal. Wasn't it you who wanted the servlet in the main source tree a year ago? On 08.02.2004 00:38:35 J.Pietschmann wrote: snip/ There ought to be a less messy approach. It could be an idea to move the various packages to different base directories, making

Re: Percentages

2004-02-09 Thread Simon Pepping
Quite a piece of work. I will try to understand it. A small correction: On Sun, Feb 08, 2004 at 10:03:57PM +0100, Finn Bock wrote: margin-[top,bottom]: width of containing block, except for page context where it ^ height (I suppose). Regards, Simon -- Simon Pepping

Re: FOP components

2004-02-09 Thread Jeremias Maerki
On 08.02.2004 01:34:16 Glen Mazza wrote: --- J.Pietschmann [EMAIL PROTECTED] wrote: - avalon and logging for the base library. The avalon jar is indeed quite small (only 25K or so), but this dependency I'd like us to eventually get rid of in favor of what Xalan does with its messaging

Re: FOP components

2004-02-09 Thread J.Pietschmann
Clay Leeds wrote: As for 1.0 (forgive my playing the devil's advocate here), why stop at 1.4? Assuming Java 1.5 will be released by the time FOP 1.0 will be released, why not base it on the latest and greatest? Would that offer any benefits? What problems might that lead to? Well, 1.4 is out

Re: FOP components

2004-02-09 Thread Jeremias Maerki
The Preferences API is exactly that: for preferences. IMO this is best for client application (GUIs) that need to save and reload preferences for the application. That's the reason for the distinction between system root and user root [1]. This is cool for our preview application and the FOP

Re: Percentages

2004-02-09 Thread Finn Bock
[Simon Pepping] Quite a piece of work. I will try to understand it. A small correction: margin-[top,bottom]: width of containing block, except for page context where it ^ height (I suppose). Well, not according to the spec:

Re: FOP components

2004-02-09 Thread Jeremias Maerki
...and I should probably help since I was the main pusher here. BTW, I've started a little something for testing the SVG transcoder using GhostScript as converter to bitmaps. I've created little Avalon components that can nicely be configured by XML. I hope I can soon upload that for you to see.

Re: FOP components

2004-02-09 Thread Jeremias Maerki
It has multiple pluggable datasources (Property files, XML, JNDI) See http://jakarta.apache.org/commons/configuration/ On 09.02.2004 01:06:08 J.Pietschmann wrote: There's also jakarta commons configuration, which uses property files (IIRC, may well be wrong). Jeremias Maerki

Re: FOP components

2004-02-09 Thread Jeremias Maerki
No, the question is: How long will it take for the 1.5 platform to establish itself? 1.4 took quite a long time, less than 1.3 but still... You will have 1.5 on Windows, Solaris and Linux immediately but all the other platforms are not so quick, even MacOSX which was promoted as the best Java

Re: JUnit test failure

2004-02-09 Thread Jeremias Maerki
I got another one. Probably a Xerces version problem. No good idea for both problems, I'm afraid. org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces. at

cvs commit: xml-fop/src/java/org/apache/fop/fo PropertySets.java

2004-02-09 Thread bckfnn
bckfnn 2004/02/09 13:30:56 Modified:src/codegen property-sets.xsl src/java/org/apache/fop/fo PropertySets.java Log: Simplefy the huge merge loop and allow compilation with jdk1.3. Revision ChangesPath 1.2 +194 -108

Re: FOP components

2004-02-09 Thread Glen Mazza
+1 --- Chris Bowditch [EMAIL PROTECTED] wrote: You would make FOP unavailable to 70% of the user base. Take a look at Sun's Xmlroff, it has a feature set comparable to the maintainance branch, its free, but FOP has a much bigger user base. Why? because xmlroff doesnt run on windows,

Re: PMC representation change, still ot ack'ed

2004-02-09 Thread Glen Mazza
Sounds good. --- Jeremias Maerki [EMAIL PROTECTED] wrote: I've just noticed that Joerg still hasn't been formally voted in in the XML PMC as a replacement for Peter. Since this was more than 2 months ago I wanted to check if this is still ok. I'll start the vote in the XML PMC on Wednesday

cvs commit: xml-fop/examples/embedding/xml/xslt projectteam2fo.xsl

2004-02-09 Thread gmazza
gmazza 2004/02/09 14:04:23 Modified:examples/embedding/java/embedding ExampleXML2PDF.java examples/embedding/xml/xslt projectteam2fo.xsl Log: Modification of ExampleXML2PDF to show a Transformer.setParameter() call. Fix to xsl stylesheet to show '1.0' instead of

Re: PMC representation change, still ot ack'ed

2004-02-09 Thread Peter B. West
Jeremias Maerki wrote: I've just noticed that Joerg still hasn't been formally voted in in the XML PMC as a replacement for Peter. Since this was more than 2 months ago I wanted to check if this is still ok. I'll start the vote in the XML PMC on Wednesday if there are no objections until then.

Re: JUnit test failure

2004-02-09 Thread J.Pietschmann
Jeremias Maerki wrote: I got another one. Probably a Xerces version problem. No good idea for both problems, I'm afraid. org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces. at