From: Henning Hraban Ramm <texml@fiee.net>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: Install fonts on MS Windows
Date: Sat, 23 Sep 2023 20:05:47 +0200 [thread overview]
Message-ID: <973781ea-947b-12fa-c139-b289dc05ad49@fiee.net> (raw)
In-Reply-To: <c8a95b61-e71b-e72d-ecff-cda521f069c9@free.fr>
Am 23.09.23 um 14:40 schrieb Jean-Pierre Delange:
> Dear list,
> I have a very simple question, perhaps too simple...
> I've installed CTX on MSWindows x64, but I can't use the fonts I've
> installed, despite the command: set
> OSFONTDIR=c:\windows\fonts;c:\windows\users\adeimantos\context\texmf\fonts.
That should be ok.
> I cleared the Windows font cache, restarted the machine, then reloaded
> with the command :
> mtxrun --script fonts --reload
That should be enough. Maybe try
mtxrun --script font --reload --force
I need that regularly for cambria.ttc to work (on OSX).
> A search for the fonts I had installed (theano didot and gfs didot) gave
> no results with :
>
> mtxrun --script fonts --list --pattern=*gfs* --all.
The pattern doesn’t need jokers. Did you try without?
> I admit that I don't know in which directory it is best to install the
> fonts for optimum performance.
If you need the fonts also for other programs, the OS directory is good,
otherwise <ConTeXt installation directory>/texmf-fonts/fonts/data/ is
recommended.
Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-09-23 18:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 13:31 [NTG-context] Toggling the symbol for the zero-width joiner and related Unicode control characters Hamid,Idris
2023-09-21 14:52 ` [NTG-context] " Hans Hagen
2023-09-21 20:53 ` Hamid,Idris
2023-09-21 21:29 ` Hans Hagen
2023-09-22 4:16 ` Hamid,Idris
2023-09-22 9:53 ` Hans Hagen via ntg-context
2023-09-22 12:39 ` Hamid,Idris
2023-09-22 13:03 ` Hans Hagen
2023-09-22 13:22 ` Hamid,Idris
2023-09-22 13:15 ` Hans Hagen
2023-09-22 13:51 ` Hamid,Idris
2023-09-22 16:44 ` Hans Hagen via ntg-context
2023-09-23 12:40 ` [NTG-context] Install fonts on MS Windows Jean-Pierre Delange
2023-09-23 17:15 ` [NTG-context] " Pablo Rodriguez
2023-09-23 18:05 ` Henning Hraban Ramm [this message]
2023-09-23 18:15 ` Wolfgang Schuster
2023-09-23 18:37 ` Jean-Pierre Delange
2023-09-23 18:56 ` Wolfgang Schuster
2023-09-23 18:30 ` Jean-Pierre Delange
2023-09-23 18:42 ` Henning Hraban Ramm
2023-09-23 19:14 ` [NTG-context] Re: Toggling the symbol for the zero-width joiner and related Unicode control characters Hamid,Idris
2023-09-24 5:50 [NTG-context] Re: Install fonts on MS Windows Andres Conrado Montoya
2023-09-24 8:04 ` Jean-Pierre Delange
2023-09-24 10:26 ` Pablo Rodriguez
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=973781ea-947b-12fa-c139-b289dc05ad49@fiee.net \
--to=texml@fiee.net \
--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).