![]() ![]() ![]() Normally, except for cases where the site creator used a url to get the TTF files directly (and this unfortunately looks quite common), all modern browsers receive files WOFF2 (and according to my personal and limited tests on macOS, no problem with them, with Safari, Firefox, Chrome). As it was pointed out in a comment ( Overlapping contours on old versions of Safari fonttools/fonttools#1281 (comment)), OTS had a bug with bit 6, and this bugged version was used up to FF 59 and Chrome 63.Probably there is a way to target browsers by platform. Especially since it's precisely to avoid a native rendering bug on macOS, if the solution creates another issue with another rendering engine, it's not good. As you point out, if it means forcing a quadrupling of rendering time by FreeType, it loses some of its interest.I don't feel like there is a problem with the WOFF2 files, so no need to leave the glyf table untransformed.įor the other formats, I don't know the creation process used by Google (but I assume it's based on fonttools and varLib), but this process would have to add bit 6 on static fonts. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |