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 11:06:52 +0200 [thread overview]
Message-ID: <20120730090651.GC7157@khaled-laptop> (raw)
In-Reply-To: <CALBOmsYN-UxQ20K2XfeWcxLKwFz9NXG3N=gvAwCHOwGhrRByrQ@mail.gmail.com>
On Mon, Jul 30, 2012 at 09:50:44AM +0200, Mojca Miklavec wrote:
> On Mon, Jul 30, 2012 at 1:05 AM, Hans Hagen wrote:
> > On 29-7-2012 22:36, Mojca Miklavec wrote:
> >>
> >> For MKII the answer is no. MKIV can - to a
> >> certain extent - read and interpret fontconfig's XML configuration
> >> file. The real question is whether ConTeXt finds the right file. On
> >> windows there is fonts.conf used by XeTeX and it might be that MKIV
> >> reads that file, but I'm not sure.
> >
> >
> > Last time I checked (more than a year ago) it did read that file.
>
> What I have in mind is that it's far from being trivial to find the
> right fonts.conf, on linux in particular. On my mac I have:
>
> /Applications/Gimp.app/Contents/Resources/etc/fonts/fonts.conf
> /Applications/MPlayer OSX Extended.app/Contents/Resources/fonts/fonts.conf
> /opt/local/etc/fonts/fonts.conf
> /usr/X11/lib/X11/fontconfig/conf.avail/05-osx-fonts.conf
> /usr/X11/lib/X11/fontconfig/conf.d/05-osx-fonts.conf
> /usr/X11/lib/X11/fontconfig/fonts.conf
>
> So feel free to guess which one to use ;)
>
> I believe that one should at least consider
> /usr/X11/lib/X11/fontconfig/fonts.conf &
> /usr/X11/lib/X11/fontconfig/conf.d/05-osx-fonts.conf in my case, but
> there is no "include the other file", so ConTeXt would actually have
> to start reading both.
fonts.conf should have something like:
<include ignore_missing="yes">conf.d</include>
no? Here it does, otherwise fontconfig itself has no way of reading
other files. But the whole thing is tricky, because the default path to
the root fonts.conf file is set into libfontconfig at build time,
ConTeXt has no way of knowing that, short of linking to libfontconfig.
> The first two files are bundled with applications (Gimp, MPlayer) and
> aso have their own caches & their own settings, so when users start
> messing and configuring the system-wide settings, those two
> applications won't obey those anyway.
Which is very pointless, there should be only one fontconfig installed
system wide, but that mac 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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-07-30 9:06 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 [this message]
2012-07-30 9:16 ` Mojca Miklavec
2012-07-30 10:31 ` Khaled Hosny
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=20120730090651.GC7157@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).