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: xits font in ~/.fonts
Date: Thu, 19 Aug 2010 00:35:52 +0200	[thread overview]
Message-ID: <4C6C6048.9020308@wxs.nl> (raw)
In-Reply-To: <3EA12B5C-730C-467A-9E33-C915FCEBA42F@uni-bonn.de>

On 18-8-2010 9:03, Thomas A. Schmitz wrote:
>
> On Aug 18, 2010, at 1:06 PM, Khaled Hosny wrote:
>
>> On Wed, Aug 18, 2010 at 01:01:13PM +0200, Taco Hoekwater wrote:
>>>
>>>
>>> Khaled Hosny wrote:
>>>>
>>>> Dunno then, it is very confusing, some fonts are found by file name and
>>>> some are not. Putting them in TEXMF tree makes them found.
>>>
>>> Wild guess: could it be related to the dot in ".fonts" ?
>>
>> Other fonts in that directory are found, font names works for all fonts
>> there too.
>>
>
> May I chime in here? Hans, a couple of weeks ago, I reported a similar problem: none of the fonts in my personal texmf-trees ends up in the database. I can still reproduce the problem:
>
> luatools AGaramondPro-Regular.otf
> /Users/tas/texmf/fonts/opentype/adobe/agaramond/AGaramondPro-Regular.otf
>
> mtxrun --script fonts --list --all "agaramond*"
>
> (i.e. nothing found). I can only use all these personal fonts via the file: syntax; name: does not work. Maybe these problems are related? Something's not quite kosher in the font database...

ah, this could be because a runtime scanned tree is not scanned for 
fonts in the database; this is somewhat disputable as such a tree is not 
expected to be stable i.e. files can come and go

i can look into it but now now (no time now) and only if there is no 
performance penalty

it's why I would always make a local tree 'databased'

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
___________________________________________________________________________________


  parent reply	other threads:[~2010-08-18 22:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-15 16:44 Aditya Mahajan
2010-08-17 13:00 ` Khaled Hosny
2010-08-17 13:08   ` Hans Hagen
2010-08-17 14:53     ` Khaled Hosny
2010-08-17 15:26       ` Hans Hagen
2010-08-17 16:01         ` Khaled Hosny
2010-08-17 16:04           ` Hans Hagen
2010-08-17 16:27             ` Michael Murphy
2010-08-18 10:57             ` Khaled Hosny
2010-08-18 11:01               ` Taco Hoekwater
2010-08-18 11:06                 ` Khaled Hosny
2010-08-18 19:03                   ` Thomas A. Schmitz
2010-08-18 20:07                     ` Aditya Mahajan
2010-08-18 22:30                       ` Hans Hagen
2010-08-18 22:35                     ` Hans Hagen [this message]
2010-08-18 22:36                     ` Hans Hagen
2010-08-18 22:48                       ` Aditya Mahajan
2010-08-18 22:50                         ` Hans Hagen
2010-08-18 22:57                         ` Khaled Hosny
2010-08-18 11:04               ` Martin Althoff
2010-08-17 23:51         ` Aditya Mahajan

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=4C6C6048.9020308@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).