-
Notifications
You must be signed in to change notification settings - Fork 1.3k
/
chromium-linux-fontconfig-renderstyle.html
47 lines (39 loc) · 1.85 KB
/
chromium-linux-fontconfig-renderstyle.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
<html>
<body>
<p>This test requires Chromium Linux <tt>test_shell</tt> in
<tt>--layout-test</tt> mode, as that forces some rendering settings used
in the following tests.</p>
<ol>
<li>
<p>The following text should render without anti-aliasing:</p>
<p style="font-family: NonAntiAliasedSans">Non anti-aliased sans.</p>
</li>
<li>
<p>The following text should be slightly-hinted Georgia. The dots
should be equally spaced, and letters in the word "government"
should be naturally spaced (without an ugly space before the "e").</p>
<p style="font-family:SlightHintedGeorgia">
government ................................
</p>
</li>
<li>
<p>The following text should be unhinted Verdana. The fontconfig
configuration for this is contradictory, setting both full-hinting
and no-hinting. The latter should win out.</p>
<p style="font-family:NonHintedSans">
Here is Tigger doing what tiggers do best … operating
hydraulic exoskeletons.
</p>
</li>
<li>
<p>The following text should show a difference caused by forcing
autohinting. Note: the effect is subtle.</p>
<p><span style="font-family:AutohintedSerif; font-size:0.6em;">autohinted</span> <i>vs</i> <span style="font-family:HintedSerif; font-size:0.6em;">not-autohinted</span></p>
</li>
<li>
<p>The following text should be the same. It verifies that, given the contradictory settings <tt>hintfull</tt> and <tt>autohint</tt>, the latter wins out:</p>
<p><span style="font-family:AutohintedSerif; font-size:0.6em;">autohinted</span> <i>vs</i> <span style="font-family:FullAndAutoHintedSerif; font-size:0.6em;">hopefully autohinted</span></p>
</li>
</ol>
</body>
</html>