(repost - I think the first one didn't get through) Now that the introductions are done, I'd like to initiate the discussion about how to actually merge jfor into FOP.
Currently I have one major code contribution to integrate into the jfor code base. I expect to be done in a week and would like to release a last "non-FOP" version of jfor with these changes. Regarding the merging of jfor, I see three options: 1) inclusion of the jfor.jar in the FOP distribution, "user-level" integration where a -rtf switch of FOP causes jfor to run instead of FOP Makes it possible for users to generate RTF + PDF without needing a separate download. No benefits on the developer side. We might get a lot of questions like "why is the RTF output so poor compared to PDF". 2) same but modify jfor to use the existing FOP infrastructure: startup, parser, configuration, logging, etc.. 3) full integration of jfor as a FOP renderer, taking advantage of the FOP analysis of the XSL-FO document. IMHO this needs to bypass the layout stage to stay quick and translate as much of the document structure as possible to RTF. Considering that I won't have much time in the next few weeks, my suggestion would be to first go ahead with 1) and simultaneously studying and discussing how to best reach 2) and 3). Any thoughts? - Bertrand --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
