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. Perhaps the best fix would be to set the char2 to a space when the next char is 0x0000. That should ensure consistency.
