ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: Font recognition with command "context", but not with command "texexec"
Date: Mon, 30 Jul 2012 01:05:15 +0200	[thread overview]
Message-ID: <5015C1AB.6040101@wxs.nl> (raw)
In-Reply-To: <CALBOmsb2d8TDC32_20NOEopf+1RRxZNVNJb-NKU2R-k4k7d39w@mail.gmail.com>

On 29-7-2012 22:36, Mojca Miklavec wrote:
> On Sun, Jul 29, 2012 at 3:39 PM, Bill Meahan wrote:
>>
>> Just curious: will ConTeXt use the fontconfig mechanism some day or are
>> there technical/philosophical reasons not to?
>
> Do you mean MKII or MKIV? 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. You 
can check that with

\enabletrackers[fonts.names]

when the database is generated.

> There is no seriously technical reason, it's more that developers
> aren't too eager to have dependencies on external libraries. And the
> fact that at least on Windows and Mac the system fonts are being
> searched for on their standard locations.

Or: "the developers never check that as they don't depend on system 
fonts in projects" (I always copy font files to known locations i.e. 
texmf-fonts).

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2012-07-29 23:05 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 [this message]
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

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=5015C1AB.6040101@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=mojca.miklavec.lists@gmail.com \
    --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).