From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: Install fonts on MS Windows
Date: Sun, 24 Sep 2023 12:26:17 +0200 [thread overview]
Message-ID: <3ed34b5b-d72a-2079-a51c-0d1e9a4f8fc2@gmx.es> (raw)
In-Reply-To: <ed6a9c08-e7bc-3766-0dd9-5e2c9e6f2efc@free.fr>
On 9/24/23 10:04, Jean-Pierre Delange wrote:
> […]
> mtxrun --script cache --erase && mtxrun --generate
> […]
> Now, I must confess that I don't know why installing new fonts in
> c:\windows\fonts, even after laboriously purging the Windows font cache
> and reloading the CTX font cache, didn't have the expected effects ...
I had the same problem on Linux, Jean-Pierre.
Before having the script to remove the cache as an option (at least, to
me), I manually deleted the contents of context/tex/temxf-cache/.
Rebuilding font cache hasn’t worked for me (most of the times), so I
came to the conclusion that generating the cache from the start worked
better for me.
The fonts installed in %WINDIR%\Fonts\ are fine. ConTeXt had a problem
adding the paths of these new fonts to its font database.
Just in case it might be clearer now,
Pablo
___________________________________________________________________________________
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-24 10:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 5:50 Andres Conrado Montoya
2023-09-24 8:04 ` Jean-Pierre Delange
2023-09-24 10:26 ` Pablo Rodriguez [this message]
-- strict thread matches above, loose matches on Subject: below --
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: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
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
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=3ed34b5b-d72a-2079-a51c-0d1e9a4f8fc2@gmx.es \
--to=oinos@gmx.es \
--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).