Both problems should by fixed now, as well as another problem with hard
breaks I found while writing the tests.
http://svn.apache.org/viewcvs?rev=326900&view=rev
On 20.10.2005 10:06:02 Jeremias Maerki wrote:
> Both are bugs. Thanks for finding them. I'm currently working on
> testing for them and
Both are bugs. Thanks for finding them. I'm currently working on
testing for them and fixing them.
On 19.10.2005 22:04:47 Simon Pepping wrote:
> Jeremias,
>
> Two questions, about SpaceResolver.resolve():
>
> 1. performSpaceResolutionRules2to3(firstPart, firstPartLengths);
>Should the resolu
Jeremias,
Two questions, about SpaceResolver.resolve():
1. performSpaceResolutionRules2to3(firstPart, firstPartLengths);
Should the resolution not be applied to the reverse of firstPart
and firstPartLengths, because you may be locating the last space
specifier in the original order?
2.
Thanks for your feedback, Simon. I know about the empty block problem.
I even documented it (sort of) in the commit message ("block w=0 causes
a fence right now although it shouldn't."). I think it relatively easily
dealt with. The box with w=0 can easily be recognized in SpaceResolver
and handled
On Thu, Oct 13, 2005 at 08:23:50PM +0200, Jeremias Maerki wrote:
> I finally uploaded my space resolution work so far. It's still not
> finished. When you go through the details you always find more stuff to
> look into and to fix. But most of it works now and is available for
> review while I work
I finally uploaded my space resolution work so far. It's still not
finished. When you go through the details you always find more stuff to
look into and to fix. But most of it works now and is available for
review while I work on the remaining issues. I assume there is room for
optimization here an