unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: James Cloos <cloos@jhcloos.com>
Cc: emacs-devel@gnu.org, miles@gnu.org
Subject: Re: The WHY of Xft
Date: Sun, 20 Mar 2005 11:49:50 -0500	[thread overview]
Message-ID: <m3r7iamfdd.fsf@lugabout.cloos.reno.nv.us> (raw)
In-Reply-To: <fc339e4a05031915475e3122f9@mail.gmail.com> (Miles Bader's message of "Sun, 20 Mar 2005 08:47:19 +0900")

>>>>> “Miles” == Miles Bader <snogglethorpe@gmail.com> writes:

>> The other benefits are just as important.  Control and installation
>> of fonts are easier for most users

Miles> Can you explain in more detail?  I use debian, and Emacs
Miles> already seems able to use the same fonts as xft-using programs,
Miles> albeit not in anti-aliased form.

That is becasue debian did the hard work for those fonts that it
includes as part of the distribution.  The hard part for users
comes when they want to install a font not part of the dist,
whether one they've purchased or otherwise acquired.

It is much easier to just drop a font into ~/.fonts than to mess
with fonts.dir and fonts.scale files, etc.  At least for those
who've not been doing so for a couple of decades....  ☺

fc-cache should be run when the contents of the searched directories
change, but cli-averse users will probably use a gui not unlike that
on doze or macs which can do that for them.  mkfontscale has helped
ease installation of server-side fonts, but it is still not as easy.

Obviously for emacs it is less of an issue than for something like
gimp, but I’m sure it will come up for some.  Especially if packages
like preview-latex can use the client-side fonts to preview the entire
document as it is being edited rather than just selected portions.

>> 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.

Miles> Doesn’t the X server already support partial loading of large
Miles> fonts?  [I mean the “-deferglyphs 16” in the X startup
Miles> options.]

I’m not familiar with deferglyphs; I don't remember it from any of
the discussions I read or participated in on the fontconfig, xfree
or freedesktop lists.  And I cannot find it in X(7x) or Xorg(1x).

My understanding is that when a (server-side) font is opened by the
X server it must determine all of the glyphs’ metrics, which requires
rendering all of them.

There are also still at least a couple of things I forgot to mention.
Server-side unicode fonts are limited to the bmp, so one cannot edit
scripts that use non-bmp characters w/o switching to client-side
fonts.  Client-side fonts are also necessary to take full advantage
of opentype features.

-JimC
-- 
James H. Cloos, Jr. <cloos@jhcloos.com>

  reply	other threads:[~2005-03-20 16:49 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             ` James Cloos [this message]
2005-03-20 22:30               ` The WHY of Xft 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=m3r7iamfdd.fsf@lugabout.cloos.reno.nv.us \
    --to=cloos@jhcloos.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).