Hey, we certainly don't mind if you look at the sources. On the contrary, we encourage people to look at it and to send in patches that help improve FOP. We're certainly reviewing the stuff that comes in. If you need any help to get started, just ask. The code-/design-level documentation may not be as extensive as you might wish sometimes, but there are always people around you can ask.
On 20.02.2006 21:21:39 b.ohnsorg wrote: > Hi there, > > besides the stats my second mail and special offer. I really like that > RTF-thingy and it's quite sophisticated documents. My RTF-XSLs were not > that neat. I've hacked some workaround for the proportional widths > coming from docbook transformations, but this is not really a good > sollution. > > So if you don't mind, I'd like to have a look at the sources and decide, > whether I have enough time for adding the necessary bits and bytes or > not. When it comes to java implementation I'm quite experienced, after a > few years of professional software development (sdk, j2ee). (Now I'm > part of the management, operating revision control systems, that sort of > thing and I'd like to return to the "classics".) > > I think it's nothing more than looking for the source of the runtime > exception, expand that code like the PDF export and there you go > (something like document.getWidth()*node.getWidthPercentage(), basically). > Hope there's enough documentation 'bout that and nobody out there being > faster than me. I wrote some very basic RTF renderer half a year ago and > had to cope with fancy tables, spannings and so on. Maybe there'll be > some free border-collapse-give-away, if there's enough time *g*. > > Thanks so far... Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
