updated Batik libraries

Team, Just updated the two libraries & source code on maintenance and HEAD. (Only took 45 minutes...not bad!) Just for reference, the process involves (for both HEAD and maintenance): 1.) CVS download of the latest Batik, compilation of it into a single jar (use batik's "ant all-jar" command to

Re: [GUMP@brutus]: xml-fop-maintenance/xml-fop-maintenance failed

I'll take care of it by this weekend, if not much sooner. Glen --- "J.Pietschmann" <[EMAIL PROTECTED]> wrote: > J.Pietschmann wrote: > > I wonder why HEAD isn't affected? > > Darn, HEAD got it too :-/ > > J.Pietschmann >

Re: [GUMP@brutus]: xml-fop-maintenance/xml-fop-maintenance failed

J.Pietschmann wrote: I wonder why HEAD isn't affected? Darn, HEAD got it too :-/ J.Pietschmann

Re: [GUMP@brutus]: xml-fop-maintenance/xml-fop-maintenance failed

Clay Leeds wrote: The thing that caught my eye is that it indicates xml-fop-maintenance. I thought the maintenance branch (fop-0_20_2-maintain) was frozen (I haven't noticed anyone updating the code--I doubt it, but could it be my manual update of the design/layout.html page? It's probably a

[Bug 29124] - New line breaking algorithm

On Tue, Aug 03, 2004 at 12:41:52PM -, [EMAIL PROTECTED] wrote: > --- Additional Comments From [EMAIL PROTECTED] 2004-08-03 12:41 --- > > Hi all > > At long last, I have finished the patch implementing Knuth's line breaking > algorithm; it took me more than I expected, mainly because

Re: Switch from AddLMVisitor to FObj.addLayoutManager()

On Tue, Aug 03, 2004 at 04:45:58AM -0700, Glen Mazza wrote: > --- Chris Bowditch <[EMAIL PROTECTED]> wrote: > > Its the > > getNextBreakPoss/addAreas methods in TextLM and > > LineLM that are scarey. > > > > Yes, that code is very complex (I wasn't able to fix a > problem with the space-after pr

Re: [GUMP@brutus]: xml-fop-maintenance/xml-fop-maintenance failed

space/ant/dist/lib/ant- launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant- nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/ local/gump/public/workspace/xml-batik/batik-20040803/lib/batik- util.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040803/ lib/bati

[GUMP@brutus]: xml-fop/xml-fop failed

jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040803/lib/batik-util.jar:/usr/local/gump/public/workspace/xml-batik

[GUMP@brutus]: xml-fop-maintenance/xml-fop-maintenance failed

l/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040803/lib/batik-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040803/lib/batik-swing.jar:/usr/local/gump/public/workspace/xml-bat

DO NOT REPLY [Bug 30448] New: - inline block render issues

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29124] - New line breaking algorithm

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29124] - New line breaking algorithm

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29124] - New line breaking algorithm

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29124] - New line breaking algorithm

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29124] - New line breaking algorithm

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29124] - New line breaking algorithm

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29124] - New line breaking algorithm

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: Switch from AddLMVisitor to FObj.addLayoutManager()

--- Chris Bowditch <[EMAIL PROTECTED]> wrote: > Its the > getNextBreakPoss/addAreas methods in TextLM and > LineLM that are scarey. > Yes, that code is very complex (I wasn't able to fix a problem with the space-after property despite much effort), and I'm not sure there's anything that can be d

Re: Switch from AddLMVisitor to FObj.addLayoutManager()

Glen Mazza wrote: Well, the number of patches and enhancements made to layout/rendering has only been about 2-3 per month in the 12 months that we've had AddLMVisitor. FOP won't finish at that rate, and that *will* affect the users. I agree that FOP wont finish at its current rate of development!

Re: Redesign

Clay Leeds wrote: On Aug 2, 2004, at 1:48 AM, Chris Bowditch wrote: Clay Leeds wrote: Just to be sure, are these amongst the changes you're looking for: Hi Clay, yes these are the changes I was looking for. If you could apply the changes manually I would be most grateful. Thanks, Chris Done. K