[NTG-context] Fwd: OSFONTDIR and Windows 10

Hans Hagen j.hagen at xs4all.nl
Thu Aug 15 23:57:50 CEST 2019


On 8/15/2019 11:06 PM, Henning Hraban Ramm wrote:
>> Am 2019-08-15 um 08:08 schrieb Huseyin Özoguz <h.oezoguz at 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
-----------------------------------------------------------------


More information about the ntg-context mailing list