Two days are quite short for that amount of information so the workshop
is quite intensive, but the feedback from past workshops was very
positive.

BTW, I’m happy to give this training (available in German or English) at
a location of your choosing (preferably within Europe). Let me know if
you are interested.

I must say: it was simply fun to work with this setup. DocBook is well documented. The documentation always had an option for all of my wishes. No wasted time, no crashes, no despair (I pity those who do this with MS Word). I can only recommend to do any larger documentation work like this.

This will make especially ODFDOM interesting for Apache FOP.  One of the missing puzzle pieces in FOP surely is an ODF output plug-in to replace the RTF format in the long run. Somehow I’ve got the feeling that we won’t have to wait all too long for that…

It’s unbelievable what these guys put together. Sometimes I had the impression that there was more interest in the OpenExpo than in the larger TopSoft that was held right beside the OpenExpo in the same hall.

For the ASF, Andreas Hartmann presented Lenya, Christian Geisert presented OfBiz and I FOP. On Thursday, I held a presentation on FOP and I was happy to have an almost full room. Many people indicated that they didn’t know FOP, yet. So, this was a really good opportunity to do a little promotion.

I had a nice long talk with Andreas Vox from the Scribus team about layout. It was interesting to learn how Scribus does line-breaking compared to FOP.

More photos should be available on the OpenExpo site shortly along with the presentations (videos plus slides).

I guess it would be interesting to present Apache FOP at the PDF/A conference. For FOP users this could also be a reason to come to Amsterdam in that week. To a certain degree you can probably combine catching up on PDF/A with interesting discussions with FOP developers. I don’t know, yet, but hopefully Vincent gets one of his session proposals on FOP accepted which would be one more reason for FOP users to come to Amsterdam.

Between 2003-07-18 and 2005-11-22 (for more than two years), there was no release of Apache FOP. Many believed the project was dead. No wonder: the majority of the project team back then gradually went away for various reasons. There was no consensus about how the project should be continued. The “maintenance branch” constantly competed for attention with the necessary redesign effort which was started back in late 2001. The XSL standard lost its “new and shiny” status at some point which obviously didn’t help attracting a lot of creative minds with a lot of free time at their hands.

Today, XSL is a mature, if complex, technology which is widely adopted and treated as a commodity taken for granted. At least that’s often my impression. I mean, if we look at the size of the user base of Apache FOP compared to the number of the active committers, the difference is huge. Still, I’m very happy that we’ve been able to attract a sizeable group of new committers to Apache FOP once again over time.

From a personal perspective, it’s so good to see various companies and even some government institutions investing in FOP. Of course, the whole open source movement is still gaining momentum which helps here. Nowadays, I can even make my living by doing freelance work almost exclusively in the Apache XML Graphics ecosystem. My clients, in turn, get added value in various forms: new features, bugfixes, professional support with good reaction times, no vendor lock-in (independance from a single commercial provider), full access to the source code, sharing of development costs, no licensing costs etc. That’s a win-win situation for everyone involved.

I’m looking forward to the time ahead. There are still many things to do. One of the most important ones: Still not having jumped over the version 1.0 barrier harms the project: some companies don’t adopt 0.x software and others won’t invest in it. I hope we can finally, finally fix that in 2008, almost ten years after the XSL standard was started. And FOP was actually the first implementation of XSL-FO available.

We will now have to take a closer look at the question, if we should directly skip to Java 1.5 as some suggested. Personally, I’m a little hesitant, since I know a lot of people who are still stuck with Java 1.4 for the moment. They all want to migrate to at least 1.5, of course, but that requires careful preparation in complex environments. Better stick to Java 1.4 until at least summer 2008 when the end-of-life process at Sun ends for Java 1.4.

As I hinted in an earlier post, I feel that SVG Print may already be coming too late (although it has been in development for more 4 years now). Mars looks more interesting (a spec update is coming up, I heard). The packaging of binary resources (images, fonts etc.) in a ZIP file is very efficient and versatile while this is sort of an unsolved problem in SVG Print. The Primer hints at the use of Multiplex MIME (RFC 3391) which is possibly more difficult to handle than a ZIP archive. Over all SVG Print gives me the impression that it’s not much more than a research project by Canon’s research labs. Not that Adobe’s Mars is much more than that right now. In that regard, Microsoft’s XPS has probably evolved further. Too bad, Mars is still my favourite approach if I had to choose an alternative to PDF.

Want to try it out in 2 minutes? Create a little math expression in OpenOffice 2.x, save it in ODF or MathML format. Then just start JEuclid’s MathViewer application using WebStart and open that file.