From: Khaled Hosny <khaledhosny@eglug.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: Font recognition with command "context", but not with command "texexec"
Date: Mon, 30 Jul 2012 12:31:08 +0200 [thread overview]
Message-ID: <20120730103108.GB10735@khaled-laptop> (raw)
In-Reply-To: <CALBOmsZFvQ53uBsRKXN=D-63kqY0w001eW6-4n-+ZmBpriCDxQ@mail.gmail.com>
On Mon, Jul 30, 2012 at 11:16:44AM +0200, Mojca Miklavec wrote:
> I believe it's the other way around: applications on Mac should not
> use fontconfig ;), but when they do (most of them being ported from
> linux), they cannot rely on fontconfig's presence on the system.
>
> It's more or less the same situation on windows. When you launch VLC,
> MPlayer, gnuplot/wxt or XeTeX after a long time, it spends the first
> minute refreshing font cache.
Right, I think fontconfig should turn itself into a warper around native
system font services on such systems and not manage a cache on its own,
which is better than porting every fontconfig using application. OT
anyway.
Regards,
Khaled
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2012-07-30 10:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-28 19:11 Martin Rimmler
2012-07-29 7:34 ` Wolfgang Schuster
2012-07-29 13:39 ` Bill Meahan
2012-07-29 20:36 ` Mojca Miklavec
2012-07-29 23:05 ` Hans Hagen
2012-07-30 7:50 ` Mojca Miklavec
2012-07-30 9:06 ` Khaled Hosny
2012-07-30 9:16 ` Mojca Miklavec
2012-07-30 10:31 ` Khaled Hosny [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=20120730103108.GB10735@khaled-laptop \
--to=khaledhosny@eglug.org \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.nl \
/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 NNTP newsgroup(s).