diff options
| author | jshin@chromium.org <jshin@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-06-16 17:42:35 +0000 |
|---|---|---|
| committer | jshin@chromium.org <jshin@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-06-16 17:42:35 +0000 |
| commit | ce16e809676fe3dd03c6a4fcb99580c600ecb91c (patch) | |
| tree | 5ffa1a3b73e7a439b800565bef676b86fd79e12c /tools/coverity | |
| parent | c99eb84ef887d8b0f58a17d7b1492d7ae8f07bb9 (diff) | |
| download | chromium_src-ce16e809676fe3dd03c6a4fcb99580c600ecb91c.zip chromium_src-ce16e809676fe3dd03c6a4fcb99580c600ecb91c.tar.gz chromium_src-ce16e809676fe3dd03c6a4fcb99580c600ecb91c.tar.bz2 | |
Map Liberation Sans Mono and Ascender Sans Mono to Courier New.
They're metrically compatible with each other, but the former is
sans serif (monospace) while ther latter is serif (monospace), which is why we didn't include this mapping in the two previous CLs (one by Evan and the other by me).
However, on ChromeOS, we use 'Ascender Sans Mono' as a substitute for Courier
New so that they have to be regarded as 'identical'.
Without this change, a text node styled with 'Courier New' is not rendered
with our replacement font while a text node styled with 'Courier New, momospace'
or 'monospace' is rendered with our replacement font.
BUG=cros:4006
TEST=See the bug.
Review URL: http://codereview.chromium.org/2838003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@49975 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools/coverity')
0 files changed, 0 insertions, 0 deletions