On 8/16/2019 7:40 AM, Henning Hraban Ramm wrote:

...

Am 2019-08-15 um 23:57 schrieb Hans Hagen :

On 8/15/2019 11:06 PM, Henning Hraban Ramm wrote:

...

...

Am 2019-08-15 um 08:08 schrieb Huseyin Özoguz :

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)

It’s been a while since I had my whole collection of literally thousands of fonts in OSFONTDIR, but re-scanning happens quite often – yes, probably something’s wrong in my typescripts, or I call for an invalid combination somewhere.

At the moment I just get this error message on every run:

resolvers | globbing | confusing filename, name: 'SourceSansPro-SemiBold.ttf', lower: 'sourcesanspro-semibold.ttf', already: 'SourceSansPro-Semibold.ttf' maybe

\enabletrackers[fonts.names,fonts.warnings,fonts.specifications,fonts.rejections] gives some clue. Normally the database is rescanned when there is a font not found (maybe new one) or the format is remade, but that then should be once. After that a bad typescript should jkust trigger missing font warnings.

I don’t understand what’s wrong with that font.

maybe nothing but some fonts can be on the system twice or have an internal name that is wrong or clashs with another one. In the worst case the clash could result in (maybe) this random hash ordering (per run), so you toggle between instances. It's anyway why I always put fonts in texmf-fonts/fonts/data, even system fonts, just to be sure that i get want i expect. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------