css - DIN-font web kerning issue -


Why does anyone consider this special character: "Å" "Really strange weird?

They look right here: Enter image details here

< The first word of the copy text shown in the screen shot is "scale", which often looks quite normal, but is not: "one" is really two letters, "div" An original Latin letter "a" remains a combination of the above U + 030A Although it is true, and the general "å" is called "canonical equivalent" by the Unicode standard, the reality is more ambiguous.

Although the canonical equivalent sequences are presented " Expected "but often it does not happen, for one thing, the font used can not be U + 030A, and then there may be strange things. In addition, in Unicode standard or HTML specifications In fact, the software is no general requirement that U + 030 A variety of supported combinations of letters at all.

This is a normal W3C policy, although it is not part of HTML specifications or drafts, generalization form C can be used. It also includes the principle, that characters like "A" are presented with their own code, not as a pair of original character and a combination diagram. See (preparing a draft which will probably change to a great extent, but there is widespread support widely in the principle of generalization).

In this specific case, the following CSS declaration applies to the text:

  font-family: DIN, Arial, Helvetica, without-serif! Important;  

What happens here is that the DIN font is used for the original Latin characters, but not for the U + 030A because there is no glyph in the character font of that character. Arial font is used for it Generally, when you combine the original character from a forest with a combination symbol with any other font, you should expect to be deteriorated or worse.

Simple Solution "A" is included in a single, "precomposed" character, U + 00E5, DIN font instead of a two-letter sequence.

Another solution is to leave the use of DIN. When the aerial is used, the combination icon works well in modern browsers, because it will now be used on the same font from the same font.

Note that you may have similar problems with other characters, such as "é" (with acute accent).


Comments