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.
No idea if the original problem is fixed yet, but it certainly isn't
any worse.
Chris
No comments:
Post a Comment