unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <snogglethorpe@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Antialiased text on X11
Date: Sat, 19 Mar 2005 09:59:57 +0900	[thread overview]
Message-ID: <fc339e4a05031816594e6bff8f@mail.gmail.com> (raw)
In-Reply-To: <d1fgl1$kbl$1@sea.gmane.org>

On Fri, 18 Mar 2005 16:21:06 -0500, Ali Ijaz Sheikh <ali@binish.com> wrote:
> > A lot of people _think_ they need AA support. Until I tell them about
> > the terminus-font that is. :-)
> 
> I think that is a generalization; and a matter of opinion.

Well, surely not, since he was relating his experience, not stating a
general rule... :-)  But I understand your point.

> The fact of the matter is that anti-aliased
> fonts specially on LCD screens look much better than non-antialiased
> fonts.

This however, _is_ a generalization, and a matter of opinion.

I use beautiful anti-aliased fonts (with sub-pixel rendering on an
LCD) every day in firefox and gnome apps (ft2's auto-hinting is
incredibly good), and I also use Emacs alongside them.  Emacs is not
noticeably less beautiful.

The reason is simply that -- like Hans -- I've found a font that I
really like which looks good without anti-aliasing.

I think that in general what Hans says is correct:  it depends very
much on the particular font whether anti-aliasing helps significantly
or not (there are certain fonts which I far _prefer_ "non-smoothed",
and wish I knew how to make ft stop smoothing just those fonts).

However Emacs not supporting anti-aliasing certainly restricts one's
choices of fonts, because many fonts out there don't look good without
AA, and one's choice of sizes, because at extremely small sizes AA
becomes much more necessary.  If a user particularly likes a font that
needs AA, he's surely going to be a bit annoyed that he can't use it
in Emacs.  Obviously you are.  :-)

So I think Emacs should definitely support AA when it can, but it's
surely not as fundamental a requirement as has been suggested...

[The question of whether to support just xft or try to go for an
entire new rendering layer like Cairo is interesting -- my impression
is that porting to a new rendering layer is actually fairly
straight-forward; it might be the easier task than figuring out the
convoluted Emacs font-selection machinery (required in either case I
guess -- but it means that "xft only" might not be any easier
really)!]

-Miles
-- 
Do not taunt Happy Fun Ball.

  parent reply	other threads:[~2005-03-19  0:59 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-10 21:45 Antialiased text on X11 James Cloos
2005-03-10 22:25 ` Stefan Monnier
2005-03-10 23:15   ` Han Boetes
2005-03-11  4:58     ` Jan D.
2005-03-18 21:21     ` Ali Ijaz Sheikh
2005-03-18 22:39       ` Drew Adams
2005-03-19 22:45         ` The WHY of Xft [was: Re: Antialiased text on X11] James Cloos
2005-03-19 23:47           ` Miles Bader
2005-03-20 16:49             ` The WHY of Xft James Cloos
2005-03-20 22:30               ` Miles Bader
2005-03-21 14:24                 ` David Hansen
2005-03-21 16:12                 ` James Cloos
2005-03-21  0:32               ` Kenichi Handa
2005-03-19  0:59       ` Miles Bader [this message]
2005-03-19  6:27         ` Antialiased text on X11 Jan D.
2005-03-19  7:39           ` Miles Bader
2005-03-19 16:31           ` Stefan Monnier
2005-03-19 16:53             ` Han Boetes
2005-03-20 11:51               ` Jan D.
2005-03-19 21:41             ` Miles Bader
2005-03-20 13:15             ` Jan D.
2005-03-20 22:51             ` Jan D.
2005-03-22 23:44               ` Miles Bader
2005-03-23  2:30                 ` Miles Bader
2005-03-23 17:50                 ` Jan D.
2005-03-25 21:40                   ` Miles Bader
2005-03-26  8:13                     ` Jan D.
2005-03-29 10:52                       ` Geoffrey J. Teale
2005-03-29 11:28                         ` Miles Bader
2005-03-29 12:24                           ` Geoffrey J. Teale
2005-03-29 18:24                           ` Henrik Enberg
2005-03-29 22:50                             ` Miles Bader
2005-03-31  2:42                               ` James Cloos
2005-03-31  4:22                                 ` Miles Bader
2005-03-29 19:28                         ` Jan D.
2005-04-01  8:15                           ` Miles Bader
2005-04-01 16:09                             ` Jan D.
2005-03-22 12:45           ` Oliver Scholz
2005-03-22 14:21             ` Stefan
2005-03-22 14:29               ` Oliver Scholz
2005-03-22 15:17                 ` David Kastrup
2005-03-10 23:19   ` James Cloos
2005-03-11  9:20     ` Geoffrey J. Teale
2005-03-11 15:13       ` Jan D.

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=fc339e4a05031816594e6bff8f@mail.gmail.com \
    --to=snogglethorpe@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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).