![](https://secure.gravatar.com/avatar/d4bd34a45c928e8356f38323ff84763e.jpg?s=120&d=mm&r=g)
Am Thu, 28 Oct 2010 16:59:34 +0200 schrieb Hans Hagen:
And when I have corrected the fontdata, is there a way (besides using a fea-file) to manipulate the fontdata so that the input "K" outputs the glyph "c140"?
I have not followed this closely, bit it seems to me that the problem is more likely caused by a fea file than that it is cured by it.
It seems like the font is using that multiple code points for the same glyph some thing of TrueType, I'm not sure, but I recall FF documentation recommending against using it.
indeed there is some multiple mapping going on and as we're dealing with sparse tables and loops over a hash we get a bit arbitrary matches when there are multiple ...
there is also some pretty high altuni field present
if I look at the font in fontforge the chess symbols sit in latin slots so it's in the font
Yes, I know that the font is a bit dubious. That's the case for quite a lot of the free chessfonts. The question I have: How can I correct the fontdata after I have loaded the font? -- Ulrike Fischer