Ticket #60 (closed defect: wontfix)
fontconfig antialiasing
| Reported by: | mickey@… | Owned by: | mickey@… |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | Theming - Gtk+ | Version: | unspecified |
| Severity: | minor | Keywords: | |
| Cc: | buglog@…, olvaffe@… | Blocked By: | |
| Blocking: | Estimated Completion (week): | ||
| HasPatchForReview: | PatchReviewResult: | ||
| Reproducible: |
Description
may not be necessary at all due to 2.8" display w/ 280dpi
Change History
comment:3 Changed 6 years ago by olvaffe@…
I've done some benchmarks on XRenderCompositeString8, by drawing "The quick
brown fox jumps over the lazy dog" with Bitstream Vera Sans, at 26pixels:
with AA + subpixel: 148 times per second
with AA : 179 times per second
without AA : 519 times per second
Although the numbers are quite impressive, glyphs still look rugged without AA.
IMO, AA is necessary.
As for subpixel rendering (which is on by default), because the color fringes
are so easily noticeable, I think it can be disabled. This helps save the
memory too. Without subpixel, only 1/4 of memory are needed to cache the same
number of glyphs.
We can consider the necessity of hinting too. With AA, and with such a high
resolution device, hinting is not a must anymore, especially when the default
build of freetype uses the CPU-intensive autohint.
comment:5 Changed 6 years ago by alphaone@…
Any progress on that? I'm quite surprised that AA is necessary on this screen.
I just tried turning off anti-aliasing and it really is kind of ugly when viewed
from close up.
So we should turn off subpixel rendering and hinting.
We need to evaluate the performance impact of the different AA settings (vs no AA).