On Fri, Dec 30, 2005 at 11:50:21PM +0800, Manuel Mall wrote: > On Fri, 30 Dec 2005 11:25 pm, Andreas L Delmelle wrote: > > On Dec 30, 2005, at 14:54, Manuel Mall wrote: > > > On Fri, 30 Dec 2005 09:38 pm, Andreas L Delmelle wrote: > > >> I explicitly excluded fo:leaders from white-space handling, > > >> because for example: > > >> > > >> <fo:leader leader-pattern="use-content"> xxx </fo:leader> > > >> > > >> Collapsing the three spaces to one may produce unintended results. > > >> > > >> OTOH, if you have a nested inline in a leader, then the > > >> white-space for the inline will be treated... > > > > > > Is there an indication in the spec that whitespace around > > > use-content leader patterns should be treated any different? If > > > not, I would include it into the normal white space handling. > > > > This was more based on expectation than on anything I encountered in > > the specs, I guess. The white-space around the leader --physically > > outside of the fo:leader element-- is treated according to the type > > of parent it belongs to. The spaces inside the content of the > > fo:leader are left alone. Somehow, even with white-space- > > collapse="true", I'd much more expect the end result to mimic: > > > > <fo:leader leader-pattern="use-content">...xxx...</fo:leader> > > > > than > > > > <fo:leader leader-pattern="use-content"> xxx </fo:leader> > > > > Actually I wouldn't (assuming default white space handling property > values). What do others think?
I agree with Manuel. The white-space-collapse value holds everywhere. The user must provide a value of false if he wants a leader pattern with multiple adjacent spaces. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl