


This principle is most noticeable in the italics where the lowercase characters are subdued in style to be at their best as elements of word-images. Diagonal and vertical hairlines and serifs are relatively strong, while horizontal serifs are small and intend to emphasize stroke endings rather than stand out themselves. It has very even spacing and proportions. Cambria Font Free DownloadĬambria has been designed for on-screen reading and to look good when printed at small sizes. This font, along with Calibri, Candara, Consolas, Corbel and Constantia, is also distributed with Microsoft Excel Viewer, Microsoft PowerPoint Viewer, 6 7 the Microsoft Office Compatibility Pack 8 for Microsoft Windows and the Open XML File Format Converter for Mac. Therefore, the Macintosh version of Cambria is packaged as individual TrueType Font (TTF) files, rather than a single TTC file. Guardian Egyptian, Elena, and Skolar are similar to Cambria but avoid monotony. It works well on screen, but on the printed page, it’s a skull-clutcher. Cambria is an example of this problem. The converse of this principle is that a font with too much consistency can be numbing to read. Cambria has been designed for on-screen reading and to look good when printed at small sizes. Diagonal and vertical hairlines and serifs are moderately powerful, even as horizontal serifs are small and intend to emphasize stroke endings as a substitute than stand out themselves. Looks like there are a couple of issues with how this has been rebased.The Cambria font has been designed for on-display reading and to seem good when printed at small sizes. So, I agree, we can ignore that.Ĭomment on attachment 8406697 The differences in these tests do not seem to be due to any problems in the font metrics, but expected from the nature of the test. The b2g results may just be amplifying those due to the apparent nearest neighbour interpolation. But there were already similar differences in the linu圆4 results. I'm guessing the biggest difference is in the sides of border2 where there seems to be a slightly different vertical alignment. > we can ignore that, and just adjust the fuzzy() annotation as needed. > positioning a bit and so the exact number of fuzzy pixels changes. > doesn't substantially change things it just happens that it perturbs the

> "massively fuzzy" in the reftest manifest, and the USE_TYPO_METRICS patch

> It turns out the border-image-element.html test is already marked as (In reply to Jonathan Kew (:jfkthame) from comment #21) prefer OS/2 sTypo* metrics to hhea ascent/descent if USE_TYPO_METRICS flag is set, and for OpenType Math fonts.
