Anti-Aliasing Disparities in @font-face Kits Across Windows and Mac
The implementation of @font-face kits using fonts from Font Squirrel can result in notable differences in rendering between Windows and Mac operating systems. Specifically, fonts may exhibit a more pronounced thickness and lack of smoothness on Windows platforms.
To resolve this issue, it has been discovered that Chrome on Windows particularly dislikes the default CSS generated by Font Squirrel. The solution lies in modifying the order of the src property in the @font-face rule.
By moving the SVG format line to the top of the list, the anti-aliasing issue can be resolved. Here's an example of the modified @font-face code:
@font-face { font-family: 'HLC'; src: url('/_styles/hlc/hl-webfont.svg#HLC') format('svg'), url('/_styles/hlc/hl-webfont.eot') format('embedded-opentype'), url('/_styles/hlc/hl-webfont.woff') format('woff'), url('/_styles/hlc/hl-webfont.ttf') format('truetype'); font-weight: normal; font-style: normal; }
This modification has proven effective in resolving the anti-aliasing disparity between Windows and Mac systems, ensuring that fonts retain the desired level of smoothness and clarity.
The above is the detailed content of Why Do @font-face Kits Render Differently on Windows and Mac?. For more information, please follow other related articles on the PHP Chinese website!