Re: [REDESIGN] Line layout manager discussion

Arved, Firstly, thanks for taking the trouble to do this. Your diagrams make your argument beautifully clear, and facilitate discussion for everyone, even XSL spec novices. Even me, who struggles to follow text-only arguments. I haven't followed all of the posting yet, but one question has

RE: [REDESIGN] Line layout manager discussion

Discussion follows below. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Karen Lease > Sent: April 29, 2002 5:39 PM > To: [EMAIL PROTECTED] > Subject: [REDESIGN] Line layout manager discussion > > Keiron Liddle wrote: > > So why flatten the inline

DO NOT REPLY [Bug 8670] - UNICODE/DBCS .FO files (like those produced by XMLSpy) cannot be processed by FOP

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://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 8661] - FOP 0.20.3 Not running on solaris 2.6 / jdk 1.3.0

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://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 8670] New: - UNICODE/DBCS .FO files (like those produced by XMLSpy) cannot be processed by FOP

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://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 8661] New: - FOP 0.20.3 Not running on solaris 2.6 / jdk 1.3.0

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://nagoya.apache.org/bugzilla/show_bu

fop 19

Does anyone know what happened to fop 19? Did the tag go away? It does not show up in a cvs status of build.xml. I ask because the starting point for my code was 19, and I would like a point nearby to branch from for my initial migration. Peter

Re: [REDESIGN] Line layout manager discussion

Keiron Liddle wrote: > Karen, > > On 2002.04.29 22:39 Karen Lease wrote: > >> It's certainly true that mixing blocks in inlines, as the spec says is >> allowed, gets very complicated. I remember some discussion of this on >> the list a long while ago and I think we actually asked the XSL editors

Re: [REDESIGN] Line layout manager discussion

Karen, Some extra topics I have been thinking about: Determining best break. (What is the level of keep broken by a hyphenation, is it 0 for hyphenating and always for not?) The best break position has an equal or lower keep value and is closer to the optimum position. If there are keeps betwe