[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ft-devel] Rendering artifacts
From: |
malc |
Subject: |
Re: [ft-devel] Rendering artifacts |
Date: |
Sat, 11 Sep 2010 01:18:05 +0400 (MSD) |
User-agent: |
Alpine 2.00 (LNX 1167 2008-08-23) |
On Thu, 9 Sep 2010, malc wrote:
> On Thu, 9 Sep 2010, Werner LEMBERG wrote:
>
> > >> > The way i understand it - Windows's rasterizer (with or without
> > >> > ClearType) processes the bytecode (or output of the BCI) differently
> > >> > so that the problem never manifests itself.
> > >>
> > >> I don't think so.
> >
> > Oops, I misunderstood the remark. You are right, the bytecode is
> > interpreted differently, at least for ClearType.
> >
> > > Sorry for forgetting to actually provide the text for [1], here goes:
> > > http://translated.by/you/why-linux-fonts-suck/original/
> >
> > Uh, oh, this article is three years old...
> >
> > And the `theory' he mentions is plain wrong: It has nothing to do with
> > the rasterizer.
> >
> > A whitepaper from Microsoft has appeared (please look up the archive
> > for an URL) which explains how ClearType actually works, and in
> > particular, what they do with legacy fonts. Three years ago, this
> > wasn't known at all.
>
> As i said earlier, the lines do not disappear under Windows whether
> you enable cleartype or regular "font smoothing", and furthermore
> if smoothing/antialiasing is enabled on (at least) Windows and Mac
> OS X - GASP is ignored.
>
I take that back and appologize, with standard font smoothing Windows
does respect GASP it seems, sorry.
--
mailto:address@hidden