From: Miles Bader <snogglethorpe@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: The WHY of Xft [was: Re: Antialiased text on X11]
Date: Sun, 20 Mar 2005 08:47:19 +0900 [thread overview]
Message-ID: <fc339e4a05031915475e3122f9@mail.gmail.com> (raw)
In-Reply-To: <m38y4jntk9.fsf@lugabout.cloos.reno.nv.us>
On Sat, 19 Mar 2005 17:45:42 -0500, James Cloos <cloos@jhcloos.com> wrote:
> It should be pointed out that antialiasing and sub-pixel rendering are
> just two of the benefits of the client-side font system brought by Xft
> and friends.
>
> The other benefits are just as important. Control and installation of
> fonts are easier for most users
Can you explain in more detail? I use debian, and Emacs already seems
able to use the same fonts as xft-using programs, albeit not in
anti-aliased form.
> fonts with large encodings -- such as
> CJKV fonts or any iso10646-encoded font -- use *much* less vm and data
> transfer between client and server is reduced for most workloads.
Doesn't the X server already support partial loading of large fonts?
[I mean the "-deferglyphs 16" in the X startup options.]
-Miles
--
Do not taunt Happy Fun Ball.
next prev parent reply other threads:[~2005-03-19 23:47 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 [this message]
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 ` Antialiased text on X11 Miles Bader
2005-03-19 6:27 ` 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=fc339e4a05031915475e3122f9@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).