ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Ciro <ciro@kavyata.com>
To: ntg-context@ntg.nl
Subject: Re: fonts not found
Date: Sun, 27 Jun 2010 19:21:17 -0400	[thread overview]
Message-ID: <AANLkTike-1cbm47_pAr8jPZ1GYGh_Gb46CuIJ8wn27xz@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinU-bTbSnAR-QiQhhhzsNXPtG3sLd95FZoTd6Wn@mail.gmail.com>

Never mind... Problem solved.

I re-installed everything and my fonts are recognized with no problem.
thank you
Ciro



On Sun, Jun 27, 2010 at 12:49 PM, Ciro <ciro@kavyata.com> wrote:
> Ok ,  I changed the subject:
>
> I just installed ConTeXt minimals, but my fonts are not found now:
>
>  "define fonts    > font with name Barnard-Oblique is not found"
>
>  font files are there, but some how context can't see them.
>
>  I ran "context --generate" and got lines like this:
>
>  MTXrun | resolvers: not saving runtime tree
>  'tree:////home/ciro/context/tex/texmf-fonts'
>  MTXrun | resolvers: not saving runtime tree
>  'tree:////home/ciro/context/tex/texmf-local'
>  MTXrun | resolvers: not saving runtime tree
>  'tree:////home/ciro/context/tex/texmf-linux'
>  MTXrun | resolvers: not saving runtime tree
>  'tree:////home/ciro/context/tex/texmf-context
>
>
>  and also ran "mtxrun --script fonts --reload" and got lines like this:
>
>  MTXrun | fontnames: scanning /home/ciro/context/tex/texmf for AFM files
>  MTXrun | fontnames: 3323 entries found, 0 AFM files checked, 0 okay
>
>  MTXrun | fontnames: globbing path /home/ciro/.fonts/**.ttf
>  MTXrun | fontnames: identifying system font files with suffix TTF
>  MTXrun | fontnames: globbing path /home/ciro/.fonts/**.TTF
>  MTXrun | fontnames: 639 system files identified, 39 skipped, 39
>  duplicates, 600 hash entries added
>
> My fonts are in $HOME/.fonts  (lunix/ubuntu)
>
> I don't use typescripts. I use
>
> \definefontsynonym [baob] [file:Barnard-Oblique] [features=default]
>
>  what should I do?
>
>  thank you
>  Ciro
>
___________________________________________________________________________________
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:[~2010-06-27 23:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-27 16:49 Ciro
2010-06-27 23:21 ` Ciro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-03-09  9:33 The requested font has no files for the 'tf' alternative Marco Patzer
2017-03-14 20:39 ` Wolfgang Schuster
2017-03-14 22:44   ` Marco Patzer
2017-03-15  7:17     ` Henning Hraban Ramm
2017-03-15  7:27       ` Fonts not found Henning Hraban Ramm
2017-03-16 21:28         ` Henning Hraban Ramm
2001-01-28  9:11 Johannes H?sing
2001-01-28 22:08 ` Hans Hagen
2001-01-29 22:34   ` Johannes H?sing
2001-01-30 17:42     ` Hans Hagen

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=AANLkTike-1cbm47_pAr8jPZ1GYGh_Gb46CuIJ8wn27xz@mail.gmail.com \
    --to=ciro@kavyata.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).