Suggestion: use true font metrics for web browsers
GoogleCodeExporter opened this issue · comments
In response to one of the Issues, the author of MacType has explained the
reason why MacType uses the "deformed" font metrics (like glyph advance width)
produced by the Windows hinter. The reason was that if the string lengths for
eg. dialog windows would change due to using correct metrics, the strings might
get clipped and layout distorted in some applications and dialog windows (like
with gdipp). In short, MacType has traded aesthethics for compatibility. I
think it was a good decision.
However, nowadays, the majority of continuous text (where the incorrect metrics
- "jumpy text" look the worst) is read as web pages in web browsers. And
browsers certainly know how to handle various fonts with various metrics. They
would have no problem if MacType used correct metrics for browsers ONLY. This
way, MacType would get compatibility AND nice-flowing, well-kerned text 90% of
the time!
What do you think?
Original issue reported on code.google.com by pktr5pk...@gmail.com
on 13 Feb 2014 at 1:14