Article View: comp.fonts
Article #2890Bug in Windows XP Type 1 font antialiasing -- help!
From: Michael
Date: Fri, 10 Aug 2007 01:55
Date: Fri, 10 Aug 2007 01:55
53 lines
3322 bytes
3322 bytes
Hi all, There's something that's been irritating me for quite a long time, and I'm a bit surprised that I can't seem to find a single mention of it on the web. The bug is this: under Windows XP, most cases where Type-1 fonts (either as Type-1 files or in OpenType format) are rendered (using the default antialiasing), they are "twice-printed" -- that is, the black stays the normal black, but all the gray edge pixels are twice as dark as they should be. This does not happen with regular TrueType fonts, or with OpenType fonts that are TrueType internally -- it only happens with Type 1 fonts, and OpenType fonts that are Type 1 internally. If you want to test the difference for yourself, try the following: open up Windows Paintbrush, and then use the text tool to type any phrase using a Type 1 font. As you type it, you will see that the edges are "too dark". However, when you click somewhere to actually render the text to the document, it is rendered correctly, without being too dark. You can verify this by typing the same text next to it, and you can compare the two directly: the text you are typing is darker around the edges. TrueType fonts do not do this, they are always consistent (and correctly anti-aliased, to my eyes). Typing a document in Wordpad results in text that is *always* too dark, using Type 1 fonts. Microsoft Word is a bit strange--the line you are typing on (and sometimes the whole paragraph) is rendered correctly, but all other paragraphs are too dark. To make comparison easy, try hitting "Print Screen" and examining the fonts close-up, and the difference will be very clear. I was wondering now, has anybody else ever noticed this? And are there any bug patches for it? It's always irritated me as I type in Microsoft Word, using Type 1 fonts, that different paragraphs in the same font render at different weights, because some of them are "overtyped". And while most people probably don't ever notice, it really bugs my graphic designer's pixel-sensitive eye... And I use XP SP2 with all updates downloaded... Comments? Michael
Technical Details
Message-ID:
<1186710908.322252.201770@z24g2000prh.googlegroups.com>Path:
arc1-ca.pugleaf.net!g2news2.google.com!postnews.google.com!z24g2000prh.googlegroups.com!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Thread: fbb79,94826b9ea11d3ec1,start X-Google-Thread: 1042b6,94826b9ea11d3ec1,start X-Google-Attributes: gidfbb79,gid1042b6,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: arc1-ca.pugleaf.net!g2news2.google.com!postnews.google.com!z24g2000prh.googlegroups.com!not-for-mail From: Michael <mjbaldwin@yahoo.com> Newsgroups: comp.fonts,adobe.typography Subject: Bug in Windows XP Type 1 font antialiasing -- help! Date: Thu, 09 Aug 2007 18:55:08 -0700 Organization: http://groups.google.com Lines: 54 Message-ID: <1186710908.322252.201770@z24g2000prh.googlegroups.com> NNTP-Posting-Host: 189.25.66.185 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Trace: posting.google.com 1186710909 17159 127.0.0.1 (10 Aug 2007 01:55:09 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Fri, 10 Aug 2007 01:55:09 +0000 (UTC) User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.12) Gecko/20070508 Firefox/1.5.0.12,gzip(gfe),gzip(gfe) Complaints-To: groups-abuse@google.com Injection-Info: z24g2000prh.googlegroups.com; posting-host=189.25.66.185; posting-account=ps2QrAMAAAA6_jCuRt2JEIpn5Otqf_w0