Re: space-start and space-end for block-areas

Really want to dig that one out again? :-) He he ;-) I guess yes. I was starting to look at all the intrusion-adjustment and -displace stuff when I stumbled upon this issue. I need to have an absolutely clear understanding of that if I want to implement side-floats correctly. Before I go int

DO NOT REPLY [Bug 40144] - [infinite loop] big cell with number-rows-spanned attribute

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 40144] - [infinite loop] big cell with number-rows-spanned attribute

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: space-start and space-end for block-areas

On 01.08.2006 09:52:42 Vincent Hennebert wrote: > > Really want to dig that one out again? :-) > > He he ;-) I guess yes. > > I was starting to look at all the intrusion-adjustment and -displace > stuff when I stumbled upon this issue. I need to have an absolutely > clear understanding of that i

DO NOT REPLY [Bug 40144] - [infinite loop] big cell with number-rows-spanned attribute

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: space-start and space-end for block-areas

> Ah yes, so this formula comes from the statement in 7.10.7 (BTW, in > case > of mixed writing modes / reference-orientations this statement is wrong; I don't think so. FOs like block-container create a viewport/reference pair. The viewport-area does the rotation, the reference-area is already

[EMAIL PROTECTED]: Project xml-fop (in module xml-fop) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-fop has an issue affecting its community integration. This issue affects 1 pr

[EMAIL PROTECTED]: Project xml-fop (in module xml-fop) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-fop has an issue affecting its community integration. This issue affects 1 pr

[EMAIL PROTECTED]: Project xml-fop-maintenance (in module xml-fop-maintenance) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-fop-maintenance has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project xml-fop-maintenance (in module xml-fop-maintenance) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-fop-maintenance has an issue affecting its community integration. This issue

Re: space-start and space-end for block-areas

On 01.08.2006 12:14:58 Vincent Hennebert wrote: > > > > Ah yes, so this formula comes from the statement in 7.10.7 (BTW, in > > > case > > > of mixed writing modes / reference-orientations this statement is wrong; > > > > I don't think so. FOs like block-container create a viewport/reference > >

DO NOT REPLY [Bug 40154] New: -

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: space-start and space-end for block-areas

On Aug 1, 2006, at 15:44, Jeremias Maerki wrote: On 01.08.2006 12:14:58 Vincent Hennebert wrote: Well, with my working copy I get the following results: When start-indent is explicitly set to "0cm" for the third paragraph, the text is placed 1 cm /left/ from the black border: http://atvaark.d

Re: space-start and space-end for block-areas

On Aug 1, 2006, at 19:53, Andreas L Delmelle wrote: Might be caused by something like: margin-left influences the start-indent property of the outer block, and this latter property is inherited... I'd debug in that direction: see what the call to PropertyList.getInherited() returns in Ind

Re: space-start and space-end for block-areas

On Aug 1, 2006, at 20:06, Andreas L Delmelle wrote: Again answering my own question/remark here: One way around this would be to exclude the inherited value of start-indent if start-indent is specified on the FO. That would make it: *either* inherited *or* explicit, and not explicit *minus*

Re: space-start and space-end for block-areas

On Aug 1, 2006, at 20:29, Andreas L Delmelle wrote: On Aug 1, 2006, at 20:06, Andreas L Delmelle wrote: Again answering my own question/remark here: Oops, sorry for the noise. Totally overlooked the outer block- container... :(