From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Linux Libertine type
Date: Thu, 23 Jul 2009 19:24:00 +0200 [thread overview]
Message-ID: <4A689CB0.7020602@wxs.nl> (raw)
In-Reply-To: <20090723164335.GA12044@khaled-laptop>
Khaled Hosny wrote:
> On Thu, Jul 23, 2009 at 06:07:37PM +0200, Hans Hagen wrote:
>> Khaled Hosny wrote:
>>> On Thu, Jul 23, 2009 at 04:34:37PM +0200, Hans Hagen wrote:
>>>> Khaled Hosny wrote:
>>>>> ConTeXt doesn't use fontconfig for detecting installed fonts, try to set
>>>>> OSFONTDIR to point where your fonts are, then run:
>>>>> mtxrun -script fonts -reload
>>>>>
>>>>> Hans, is it possible to read fontconfig files to detect font directories
>>>>> on linux, it is xml files and we would be interested in <dir> and
>>>>> <include> tags only.
>>>> it does, given that the file can be found someplace in the tree (i
>>>> added a log message so that one can see of it is found)
>>> The standard places for fontconfig files are ~/fonts.conf and
>>> /etc/fonts/fonts.conf, any other file is included from there, so may be
>>> it should check for those two by default (if it doesn't already).
>> no, not there but before I even start thinking about adding that we need
>> to investigate all places as i'm pretty sure that on the mac it's
>> different (somehow 'standard' in practice is never 'standard') and
>> there's also the order to consider, one, more, and in what order then
>
> What I wrote above is for linux (I assumed the code is checks for OS and
> sets default font paths), /etc/fonts/font.conf is read first followed by
> any files included from it, then ~/.fonts.conf so that user can override
> system settings.
> (http://www.fontconfig.org/fontconfig-user.html has more details)
well, even the user file has to be specified so we can
- first look for a config file in the tex tree
- and if not found then load the etc one
i've added some logic to the locator but i didn't not test it (the linux
servers are production machines that i don't want to touch and i have no
time anyway)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-07-23 17:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 13:50 Derek CORDEIRO
2009-07-23 14:21 ` Khaled Hosny
2009-07-23 14:34 ` Hans Hagen
2009-07-23 14:39 ` Khaled Hosny
2009-07-23 16:07 ` Hans Hagen
2009-07-23 16:43 ` Khaled Hosny
2009-07-23 17:24 ` Hans Hagen [this message]
2009-07-23 14:35 ` Derek CORDEIRO
2009-07-23 14:45 ` Khaled Hosny
2009-07-23 15:00 ` Aditya Mahajan
2009-07-23 15:04 ` Derek CORDEIRO
2009-07-23 16:50 ` 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=4A689CB0.7020602@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.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).