14.8.2011 17:51, Doug Ewell wrote:
This sounds like Jukka expects browsers to analyze the glyph assigned in the font to the code position for 'a' and decline to display it if it doesn't look enough like an 'a' (rejecting, for example, Greek 'α'). I'm not sure that is a reasonable expectation.
That wouldn’t be reasonable, but what I expect is that fonts have information about the characters that the glyphs are for and browsers use that information. Something like that is required for implementing the CSS font matching algorithm:
http://www.w3.org/TR/CSS2/fonts.html#algorithm -- Yucca, http://www.cs.tut.fi/~jkorpela/
