(Sorry for the delayed reply...)
On Nov 16, 2005, at 01:15, Manuel Mall wrote:
On Wed, 16 Nov 2005 03:45 am, Jeremias Maerki wrote:
Sounds like a good plan to me. Would you go after that?
Sure thing. For now, I'll restrict it to moving handleWhitespace()
into a separate class, maybe one i
On Thu, 17 Nov 2005 03:40 am, Simon Pepping wrote:
> On Wed, Nov 16, 2005 at 08:15:47AM +0800, Manuel Mall wrote:
> linefeed-treatment is a local operation on a single character.
>
Yes
> white-space-collapse does not cross FO boundaries because the spec
> limits this to sibling character FOs.
>
Y
On Wed, Nov 16, 2005 at 08:15:47AM +0800, Manuel Mall wrote:
> I have no problems with the suggestion to move the white space handling
> from Block into its own class so other fo's that need it can make use
> of it.
>
> However, I still need to be convinced that pushing it down to inline
> leve
Well, my fault. I didn't so much follow the whole whitespace discussion
to know every detail. I assumed there was some kind of consensus by now.
On 16.11.2005 11:15:48 Chris Bowditch wrote:
> Jeremias Maerki wrote:
>
> > Sounds like a good plan to me. Would you go after that?
>
> Jeremias: I hav
Jeremias Maerki wrote:
Sounds like a good plan to me. Would you go after that?
Jeremias: I have similar concerns to Manuel about this. Moving the
handleWhitespace method to a different class is probably okay, but I
don't think we should start making any major changes to Whitespace
handling
On Wed, 16 Nov 2005 03:45 am, Jeremias Maerki wrote:
> Sounds like a good plan to me. Would you go after that?
>
I have no problems with the suggestion to move the white space handling
from Block into its own class so other fo's that need it can make use
of it.
However, I still need to be convin
Sounds like a good plan to me. Would you go after that?
On 15.11.2005 18:06:13 Andreas L Delmelle wrote:
> On Nov 15, 2005, at 10:03, Jeremias Maerki wrote:
>
>
> > The fix is probably to extract handleWhitespace
> > from Block into a separate class and call it from Block and Marker.
>
> In thi
On Nov 15, 2005, at 10:03, Jeremias Maerki wrote:
The fix is probably to extract handleWhitespace
from Block into a separate class and call it from Block and Marker.
In this respect: I still wonder whether it wouldn't be more
convenient to split up the whitespace handling, and deal with the
Debugging shows:
The FOText instances under fo:marker (just before and after the fo:block)
don't get processed for whitespace treatment. Block.handleWhitespace
isn't accessible to it. That's why the whitespace isn't removed and
causes additional lines. The fix is probably to extract handleWhitespac