Re: svn commit: r239375 - /xmlgraphics/fop/trunk/publish.xml

I finally managed to use ForrestBot for FOP's website. I've test-deployed it to http://xmlgraphics.apache.org/fop/. When everything looks fine there (need to wait for the rsync first), I'll try to write the necessary .htaccess file(s) in xml.apache.org/fop to redirect the old site to the new one. O

FOP website, release preparations: refactoring necessary

While we're at it: In preparation for the first release we need to start thinking about a refactoring of our website. Since FOP 0.20.5 will probably stay the preferred productive version for some time and FOP Trunk is substantially different, I'd like to propose doing a version split like Forrest [

Re: StAX, JAXP 1.4

Elliotte Harold wrote: Peter B. West wrote: But of course, I'm talking about Folio, which was built on a pull-parsing model before I had ever heard of pull-parsing, because it was the screamingly obvious thing to do. It gives me acute pleasure to see my original design decisions vindicated b

Re: FOP website, release preparations: refactoring necessary

I would like to take care of that. I should have some free time in the next few weeks, so I will start doing a little bit everyday starting Wednesday. Patrick Jeremias Maerki wrote: While we're at it: In preparation for the first release we need to start thinking about a refactoring of our w

Re: FOP website, release preparations: refactoring necessary

Very cool! Thanks a lot! If you need any help, just yell. On 23.08.2005 14:37:38 Patrick Paul wrote: > I would like to take care of that. I should have some free time in the > next few weeks, so I will start doing a little bit everyday starting > Wednesday. > > Patrick > > Jeremias Maerki wrot

Re: FOP website, release preparations: refactoring necessary

I would be willing to help in any way I can... One thing I've noticed, is that Forrest 0.7 appears to have created separate versions of their documentation. It may make sense to follow their example: Web Maestro Clay On Aug 23, 2005, at 5:41 AM,

enhancing rtf support

Hello fop-team, i'd like to spend again some time with enhancing the RTF support. I have been inactive for over a year now (sorry, i was quite busy). Do you want me to send patches, because i was inactive for such a long time? Or can i access the svn repository? I have received the fop-dev-mailing

Re: enhancing rtf support

Welcome back! On 23.08.2005 20:12:21 Peter Herweg wrote: > Hello fop-team, > > i'd like to spend again some time with enhancing the RTF support. I have > been inactive for over a year now (sorry, i was quite busy). Do you want me > to send patches, because i was inactive for such a long time? Or

Non-implemented props: border-*-precedence

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, Back from holiday, and just started work on the collapsing border model (something I discussed thoroughly with Jeremias a while ago --don't worry, I'm not going to start all over :-) ) Let me just say that, where earlier on I didn't have a

Re: Non-implemented props: border-*-precedence

On 23.08.2005 21:01:13 Andreas L Delmelle wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi all, > > Back from holiday, and just started work on the collapsing border model > (something I discussed thoroughly with Jeremias a while ago --don't > worry, I'm not going to start all o

.htaccess file for the old FOP website

FYI, I've added a .htaccess file with the following content to the /www/xml.apache.org/fop/ directory: Redirect /fop/ http://xmlgraphics.apache.org/fop/ I hope this is correct. In case the old website acts up you can still rename the file. Too bad we can't force a local rsync to quickly preview.

Re: Non-implemented props: border-*-precedence

Andreas L Delmelle wrote: Hi all, Back from holiday, and just started work on the collapsing border model (something I discussed thoroughly with Jeremias a while ago --don't worry, I'm not going to start all over :-) ) Let me just say that, where earlier on I didn't have a clear idea on what

Re: Non-implemented props: border-*-precedence

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Aug 23, 2005, at 22:09, Finn Bock wrote: Andreas L Delmelle wrote: The type should be a number with added 'force' enum. The number property will then coerce a 'force' value into an EnumNumber which is a number that also holds a enum value, b

Re: Percentages in XSL-FO

On Sat, 20 Aug 2005 11:33 pm, Jeremias Maerki wrote: > Looks like you made a thorough analysis. What I read made sense to me > although I didn't check everything to the last character. Providing > the Context interface through the LayoutContext didn't occur to me > and I don't know if it's the righ