From: Miles Bader <miles@gnu.org>
Cc: Werner LEMBERG <wl@gnu.org>, usenet@fischman.org, emacs-devel@gnu.org
Subject: Re: Xft support (freetype, anti-aliasing) in X11 emacs
Date: Sat, 5 Oct 2002 21:08:18 -0400 [thread overview]
Message-ID: <20021006010818.GA7340@gnu.org> (raw)
In-Reply-To: <200210060007.g9607IdC027101@stubby.bodenonline.com>
On Sun, Oct 06, 2002 at 01:44:43AM +0200, Jan D. wrote:
> To me anti aliased fonts don't look smoother, they just look out of focus.
> My stupid eyes tries to focus, but to no avail, since the "out of focus"
> isn't really real. I get a headache instead.
Isn't it generally held that only very large and very small type sizes should
be anti-aliased? I find that in both these cases, it helps quite a bit,
though with large fonts I suppose it's more of an aesthetic improvement than
anything else. I'd think that any decent system would allow you to set the
thresholds where antialiasing kicks in...
Part of the problem, of course, is when you simply don't have a good range of
hand-made bitmap fonts, and have to use scalable fonts -- and scalable fonts
at small sizes are often almost unreadable without anti-aliasing, and usually
pretty ugly even at `normal' sizes. [also, complicated characters like those
in Chinese/Japanese are often unreadable even at `normal' sizes in scalable
fonts; maybe all the fonts I use have sucky hinting or something though]
-Miles
--
P.S. All information contained in the above letter is false,
for reasons of military security.
prev parent reply other threads:[~2002-10-06 1:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 22:27 Xft support (freetype, anti-aliasing) in X11 emacs Ami Fischman
2002-10-03 9:10 ` Colin Walters
2002-10-04 15:46 ` Richard Stallman
2002-10-03 14:53 ` Richard Stallman
2002-10-03 18:11 ` Jan D.
2002-10-03 19:28 ` Ami Fischman
2002-10-03 20:03 ` Jan D.
2002-10-04 11:32 ` Werner LEMBERG
2002-10-05 23:44 ` Jan D.
2002-10-06 1:08 ` Miles Bader [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021006010818.GA7340@gnu.org \
--to=miles@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=usenet@fischman.org \
--cc=wl@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).