On Sun, 18 May 2014 17:03:25 +0100, Michael Drake wrote:
>
>
> On 18/05/14 13:51, Chris Young wrote:
> > On Fri, 16 May 2014 22:52:23 +0100, Michael Drake wrote:
> >
> >> there's a chance I've broken it further if ESetInfo can't handle char2
> >> being 0x0000.
> >
> > I've told it to skip kerning against 0x0000, as that makes no sense
> > anyway.
>
> OK, but if kerning against a space is any different to no kerning, then
> that's the problem. I was hoping that ESetInfo would treat 0x0000 the
> same as space.
Right. I'm getting the same effect with 1887 and 1888 though.
I'm not convinced this is the problem. It seems to be if a
sentence wraps over to the next line, if the last word on the first
line fits on the exact pixel boundary, then NetSurf suddenly decides
it doesn't fit as soon as backspace is pressed. Typing more
characters then resets it back to thinking the original number of
characters fit onto that line (and that last word moves back up).
Me deleting and typing at the end of the second line shouldn't make
any difference to the pixel count of the first line, but somehow it
does.
> Perhaps the best fix would be to set the char2 to a space when the next
> char is 0x0000. That should ensure consistency.
I've just disabled kerning in that function and it makes no difference
whatsoever - even down to the same line causing the problem (even
though it should now have a different width?)
Chris
No comments:
Post a Comment