From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin-apps@cygwin.com
Subject: Re: fontconfig packaging suggestion
Date: Fri, 04 Apr 2014 09:08:00 -0000 [thread overview]
Message-ID: <533E7696.3080302@users.sourceforge.net> (raw)
In-Reply-To: <20140404084006.GE2508@calimero.vinschen.de>
On 2014-04-04 03:40, Corinna Vinschen wrote:
> On Apr 3 18:52, Ken Brown wrote:
>> 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?
The concern is definitely valid and I'm considering various options.
> I'm not Yaakov, but, may I throw in a dumb idea?
>
> What if fontconfig installs scripts for sh and csh in /etc/profile.d,
> which has only one task: It checks if the fc cache is older than the
> modification date of the Windows fonts directory. If so, it either
> calls fc-cache or, if that takes too long, it simply informs the user
> in distinct words that fc-cache needs running.
>
> Would that work? Does it make sense?
That's one option, but I'm not sure yet if it covers all possible scenarios.
Yaakov
prev parent reply other threads:[~2014-04-04 9:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 22:52 Ken Brown
2014-04-04 8:40 ` Corinna Vinschen
2014-04-04 9:08 ` Yaakov (Cygwin/X) [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=533E7696.3080302@users.sourceforge.net \
--to=yselkowitz@users.sourceforge.net \
--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).