From: "Huseyin Özoguz" <h.oezoguz@mmnetz.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: OSFONTDIR and Windows 10
Date: Thu, 15 Aug 2019 08:08:35 +0200 [thread overview]
Message-ID: <538239a5-ffdc-21df-ddc0-19242473b3af@mmnetz.de> (raw)
Hello,
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?
Thank you.
--
Huseyin Özoguz
Schilfweg 52a
27751 Delmenhorst
E-Mail: h.oezoguz@mmnetz.de
Tel.: 0176/20203416
___________________________________________________________________________________
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 reply other threads:[~2019-08-15 6:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 6:08 Huseyin Özoguz [this message]
2019-08-15 6:36 ` Huseyin Özoguz
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=538239a5-ffdc-21df-ddc0-19242473b3af@mmnetz.de \
--to=h.oezoguz@mmnetz.de \
--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).