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>
Subject: Re: fonts and luatex
Date: Mon, 14 Apr 2008 19:43:22 +0200	[thread overview]
Message-ID: <480397BA.9080602@wxs.nl> (raw)
In-Reply-To: <20080414163216.GW31022@phare.normalesup.org>

Arthur Reutenauer wrote:
>> (i think that i wrote a fc-whatever parser but then one needs to tell 
>> where it lives etc etc)

it's rather trivial to support it

>   If fontconfig is correctly installed, you shouldn't need to do
> anything special: only run fc-list / configure fontconfig the normal way
> (probably by editing things like /etc/fonts/local.conf).

well, we only need the path in mkiv; personally i prefer setting an env 
var instead of editing yet another configuration file

>   This certainly is a good idea; I thought about it myself.  It could
> “unify” font searching with XeTeX (although it won't make the overall
> system easier to understand!).

i'll upload a beta that looks at the file; the relevant code is in 
font-syn; i.e. only named fonts will be seen because the file is not 
consulted otherwise

     local name = fonts.names.xml_configuration_file
     if name and not name == "" then
         local name = input.find_file(instance,name,"other")
         if name ~= "" then
             collect(xml.collect_texts(xml.load(name),"dir",true))
         end
     end

i'm wondering ... if a name is not found, i can regenerate the database 
at runtime. i had that for a while; maybe i should reinstate that

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
___________________________________________________________________________________

  reply	other threads:[~2008-04-14 17:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-13 11:14 Antoine Junod
2008-04-13 11:33 ` Hans Hagen
2008-04-13 12:25   ` Antoine Junod
2008-04-13 13:32     ` Hans Hagen
2008-04-13 22:02   ` Olivier Guéry
2008-04-13 22:28     ` Hans Hagen
2008-04-14  0:00       ` Yue Wang
2008-04-14  9:38         ` Olivier Guéry
2008-04-14  9:49           ` Wolfgang Schuster
2008-04-14 10:15             ` Olivier Guéry
2008-04-14 11:28               ` Wolfgang Schuster
2008-04-14 12:16           ` Mojca Miklavec
2008-04-14 13:32             ` Hans Hagen
2008-04-14 15:37               ` Olivier Guéry
2008-04-14 16:32               ` Arthur Reutenauer
2008-04-14 17:43                 ` Hans Hagen [this message]
2008-04-14 23:09                   ` Mojca Miklavec
2008-04-15  8:32                     ` Hans Hagen
2008-04-13 22:53     ` Arthur Reutenauer

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=480397BA.9080602@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).