DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=37236>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=37236 ------- Additional Comments From [EMAIL PROTECTED] 2005-11-14 14:29 ------- (In reply to comment #11) > Patch #10 applied. Thanks. > I'm looking forward to moving the Transcoders out after the FOP release. :-) It will likely make this stuff easier to track. > Is there anything outstanding concerning this bug or can we close it? As I see it there are two outstanding issues: 1) 'Complex' patterns on Text - While it is probably a 5% case it's bad that things won't work. 2) The overflow for pattern case being commented out. I would lean towards saying this is still broken enough to leave the bug open, but it's not my bug DB (so to speak). Having it open makes it at least possible that someone will have an answer to their question. > It starts to get confusing which patches are to be applied and > so on. Yes, I strongly considered going to a single PDFTranscoder patch instead of trying to track everything seperately. > I assume you'll also help track the currently commented part that > we'll have to uncomment as soon as we can rely on a later Batik version. I'll try and make sure of it. What do you think of a Batik 1.6.1 release? There are a number of small but significant improvements in Batik since 1.6.1. The real hurdle would be straightening out the XML lib lincensing (which really needs to be fixed anyways). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
