public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps <cygwin-apps@cygwin.com>
Subject: fontconfig packaging suggestion
Date: Thu, 03 Apr 2014 22:52:00 -0000	[thread overview]
Message-ID: <533DE610.4020106@cornell.edu> (raw)

Yaakov,

There is a problem with having fontconfig include the Windows Fonts 
directory in /etc/fonts/fonts.conf.  Namely, the font cache for that 
directory is very likely to be out of date [*], but most users have no 
idea that they need to run fc-cache to keep it up to date.  This can 
cause slowdowns or worse for applications that use fontconfig.  See, for 
instance http://cygwin.com/ml/cygwin/2013-12/threads.html#00246 and 
several similar reports that came later.

I propose that fontconfig *not* include the Windows Fonts directory, but 
that a new package (perhaps called fontconfig-windows-fonts) be created 
that takes over this functionality.  This could either be a subpackage 
of fontconfig or an independent package, in which case I would be glad 
to maintain it.

This package would handle the Windows Fonts directory by creating the 
appropriate file in /etc/fonts/conf.d, and it would also provide a 
script that calls fc-cache to update the Windows Fonts cache.  The 
release announcement would warn users that the script should be called 
whenever the Windows Fonts directory changed.  And I would explicitly 
advise emacs-X11 users *not* to install the package unless they really 
want to be able to use Windows fonts while running emacs under X.

WDYT?

Ken

[*] This can happen because of a Windows Update, or because software was 
added or removed, or because the user knowingly installed or removed fonts.

             reply	other threads:[~2014-04-03 22:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03 22:52 Ken Brown [this message]
2014-04-04  8:40 ` Corinna Vinschen
2014-04-04  9:08   ` Yaakov (Cygwin/X)

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=533DE610.4020106@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin-apps@cygwin.com \
    /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.
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).