From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Henning Hraban Ramm <texml@fiee.net>
Subject: Re: Fwd: OSFONTDIR and Windows 10
Date: Thu, 15 Aug 2019 23:57:50 +0200 [thread overview]
Message-ID: <8231b3a3-c1d6-084b-5199-c0406af79565@xs4all.nl> (raw)
In-Reply-To: <4FDE4510-2664-4D1E-9D7D-F253A8E5C913@fiee.net>
On 8/15/2019 11:06 PM, Henning Hraban Ramm wrote:
>> Am 2019-08-15 um 08:08 schrieb Huseyin Özoguz <h.oezoguz@mmnetz.de>:
>>
>> I just moved to Win 10 (coming from Win 7) with a fresh system and installed Context.
>>
>> My problem: The manual installed fonts are not stored in "Windows/Font" like before, but in "AppData/Local/Microsoft/Windows/Fonts" – the default Fonts, which came with windows, are still there in Windows/Font.
>>
>> If I change OSFONTDIR to the new path and execute "mtxrun --script font --reload" after that, the new fonts are found by Context, but that seems no good way, because now the default-fonts are not found.
>>
>> How to solve this situation? How can I prevent Win10 from installing manual installed fonts into this other path and instead install it into "Windows/Font"directly? (Other programs like Corel etc. have no problems finding those other fonts, regardles of there location or OSFONTDIR.)
>>
>> Another solution: Give Context two pathes to look for fonts, is that possible?
>
>
> OSFONTDIR is like other PATH variables, it can contain several paths, separated by ; (at least on Linux and OSX, maybe it’s : on Windows). My OSFONTDIR is rather lengthy to include my collections of commercial and free fonts (beware, that makes ConTeXt slow).
in what sense slow ... more fonts means of course a longer
identification time when the database is made but that happen seldom
(unless you refer to an unknown font in your document in which case a
scan happens, but that should then be fixed in the style)
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-08-15 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9BAE7219-2E4C-4B84-B0C3-C5F67D3FFCC2@fiee.net>
2019-08-15 21:06 ` Henning Hraban Ramm
2019-08-15 21:57 ` Hans Hagen [this message]
2019-08-16 5:40 ` OSFONTDIR Henning Hraban Ramm
2019-08-16 6:14 ` OSFONTDIR 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=8231b3a3-c1d6-084b-5199-c0406af79565@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=texml@fiee.net \
/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).