@font-face problem, Firefox adds padding, Chrome does not -


When the custom font is used through @ font-face , this is equally Renders as much as I think Chrome should be in Firefox, however, extra padding (top and bottom) is added to the font.

Can I do anything about it?

FYI, it happens on Linux in Firefox (and not in Chromium). I tried to load my font and immediately received a warning:

The following table (fonts) in the font has been ignored by fontfreeze.
Ignoring 'LTSH' linear threshold table
'VDMX' is the vertical device metric ignoring table.
'HDMX' horizontal device metric table Ignoring

I think the problem is that the rhythm The drawback:

Avoid to avoid grid, fitting the entire font to determine the correct height, is defined VDMX table.

It looks exactly what happens in Firefox: The minimum and maximum height is calculated incorrectly. It is also obvious when you choose text: the selection box extends up and down the line; If the h1 element was actually padding, you would see the difference between the top and bottom of the line and the selection box. Apart from this, verification shows that almost every glyph "":

Both PostScript and TrueType gives you points on the maximum of the path and the minimum (extratra)

A quick demonstration:

I had only one other problem, there was a bad situation called "Missing point points extramma" With a font, there is a point (or node, as is said in Inkscape). On the right side, right, up and down, should be on a glyph. Generally they are anyway because your glyph is formed, but with diagonal goals, diagonal lines often cause problems.


Comments

Popular posts from this blog

Eclipse CDT variable colors in editor -

AJAX doesn't send POST query -

wpf - Custom Message Box Advice -