Batik & Fop rock

I just had to buy some Batik artwork while I was in China late last year. Not because im a fan of the production process (an amazing amount of craft & effort), but because Batik the Apache SVG tools are just so awesome.

Most of Inkscapes initial coding for SVG compliance was checked against Batik as a role model for valid renderings from the SVG spec. But this is not why I had to have some Batik of my very own.

FOP and batik are essential parts of the professional open source publishers dream tool-chain.

Even graphics geeks like me can look at graphical admonitions in a book ( you know those Tip, Warning, Note & Caution callouts we see in technical documentation ) and throw in some Inkscape generated SVG icons and volla. Automated builds of PDFs now contain 100% sexy vector callouts.

Even technical illustrations/diagrams come out great and because they are single source managed in SVG we can translate whole books right down to terminology in illustrations in one simple build.

When it comes to any large print run of single materials like cd covers boxes, posters and cards I’m the first to jump into a session of Scribus. but when it comes to translating & building from docbook and xml FOP FOP FOP batik & inkscape fop fop rinse & repeat.

toolchain workflow

2 Responses to “Batik & Fop rock”

  1. Kurt Witschi Says:

    Hallo, I must say this looks like what i’m looking for. I write & coordinate plenty of technical documentation (service manuals). Could you let me know
    abit mor about your actual workflow? E.g. what sort of editor do you use for the original content? does your system have revision controll built in somewhere? what exactly is the software on the bulid machine? many thanks
    for your answers
    kurt

  2. Andy Fitzsimon Says:

    Kurt, I’ve posted some more details about the translation workflow on http://andy.brisgeek.com/archives/45

Leave a Reply