> -----Original Message----- > From: Jeremias Maerki [mailto:[EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] >
Hi, Not being subscribed to [EMAIL PROTECTED], I'm posting on fop-dev for the time being (besides this, I'm a bit hesitant on whether I should even be responding in the first place --if anyone thinks this should be added to the wiki, just yell): > Concerning the proposed TLPs I'm wondering if FOP and Batik shouldn't go > together somehow. Both projects deal with XML to graphics conversions. > FOP currently has 2 Batik Transcoder implementations (additional output > formats for Batik: PDF, PS/EPS). So there is some kind of overlap which > needs to be dealt with sooner or later. One possibility is to move the > transcoders over to Batik but parts of them are FOP-specific so both > projects should somehow be able to work on the common code. Moving these > out of FOP still means a dependency on FOP's PDF, PostScript and font > support code. These might need to be separated into "Commons" projects > to be accessible to both projects and to ensure compatibility and > cooperation. I agree, and don't want to come across as greedy here, but when it comes to use-cases, fact remains that you can have XSL-FO w/ embedded SVG, but not the other way around. (and for that matter: AFAICT XSL-FO can be rendered to SVG, but not the other way around... this could, of course, change if the two projects in question were merged somehow) On top of that, judging solely from user-list traffic, FOP seems to have had nearly thrice the attention Batik has (dev has been almost seven times as busy). Ok, maybe it takes our users three messages to explain them something, and maybe our developers are even worse :) No, I definitely see this as a pointer to the wideness of usage. I certainly support the idea of integrating the two projects one way or another. As I understand, there's a bunch of talented developers at batik-dev, so I would certainly welcome a closer cooperation between the two teams. In the long term, I think it would also be a benefit for the two specs (SVG / XSL-FO), if they become more and more directed towards combined usage, making SVG users aware of the possibilities of XSL-FO and vice versa. A combined user-list might be a good starter... Cheers, Andreas
