> -----Original Message----- > From: Glen Mazza [mailto:[EMAIL PROTECTED] > > I added in a new Batik extension element mapping in > our main trunk code--this should help you. It is not
Glen, I'm just being curious: did my remarks turn out to be helpful here? (I just want to check to what extent I'm beginning to understand the internals of the application...) > > Please test it out--wait 6 hours for a nightly > snapshot to appear (see our Download link on the main Have done so. Well, not the Batik extension element mapping in particular, but I had been embedding the maintenance version up to now. Switched it to 1.0dev and basic functionality seems to be A-OK. I've run into a few cases though where the maintenance version did its work just fine, but 1.0dev seems to be 'unfinished' - as mostly happens with nightly builds, I guess. I'm not sure which of these problems are already being worked on, and as I most certainly do not want to end up 'spamming' fop-dev with a bunch of pseudo-bugs, I'll just name a few here. If there's little insects crawling around in here you think I'd better report to Bugzilla, just let me know : 1. links ( internal & external ) don't work: neither in my own documents, nor in the newlinktest.fo example that comes with FOP 2. background-color [? this might be working fine: I defined a bg-c for a table-body - now seems to disappear; works if I add them to table-cell instead of table-body - so could be that it now actually is working correctly by 'covering' the background of body with that of the cell... I still need to check the spec & run a few tests to see whether this behaviour is compliant: CSS seems to silently presuppose that if no bg-c is explicitly defined, table-cell would inherit the value of its parent - in this case table-row, but as none was specified there either, one would expect it to be the color of table-body... ] 3. break-before & -after seem to have no effect Read you later. Greetz, Andreas
