ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
* Fwd:  OSFONTDIR and Windows 10
       [not found] <9BAE7219-2E4C-4B84-B0C3-C5F67D3FFCC2@fiee.net>
@ 2019-08-15 21:06 ` Henning Hraban Ramm
  2019-08-15 21:57   ` Hans Hagen
  0 siblings, 1 reply; 4+ messages in thread
From: Henning Hraban Ramm @ 2019-08-15 21:06 UTC (permalink / raw)
  To: mailing list for ConTeXt users

> 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).

Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD


___________________________________________________________________________________
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
___________________________________________________________________________________

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Fwd: OSFONTDIR and Windows 10
  2019-08-15 21:06 ` Fwd: OSFONTDIR and Windows 10 Henning Hraban Ramm
@ 2019-08-15 21:57   ` Hans Hagen
  2019-08-16  5:40     ` OSFONTDIR Henning Hraban Ramm
  0 siblings, 1 reply; 4+ messages in thread
From: Hans Hagen @ 2019-08-15 21:57 UTC (permalink / raw)
  To: mailing list for ConTeXt users, Henning Hraban Ramm

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
___________________________________________________________________________________

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: OSFONTDIR
  2019-08-15 21:57   ` Hans Hagen
@ 2019-08-16  5:40     ` Henning Hraban Ramm
  2019-08-16  6:14       ` OSFONTDIR Hans Hagen
  0 siblings, 1 reply; 4+ messages in thread
From: Henning Hraban Ramm @ 2019-08-16  5:40 UTC (permalink / raw)
  To: mailing list for ConTeXt users

> Am 2019-08-15 um 23:57 schrieb Hans Hagen <j.hagen@xs4all.nl>:
> 
> 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)

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'

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


Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD

___________________________________________________________________________________
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
___________________________________________________________________________________

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: OSFONTDIR
  2019-08-16  5:40     ` OSFONTDIR Henning Hraban Ramm
@ 2019-08-16  6:14       ` Hans Hagen
  0 siblings, 0 replies; 4+ messages in thread
From: Hans Hagen @ 2019-08-16  6:14 UTC (permalink / raw)
  To: mailing list for ConTeXt users, Henning Hraban Ramm

On 8/16/2019 7:40 AM, Henning Hraban Ramm wrote:
>> Am 2019-08-15 um 23:57 schrieb Hans Hagen <j.hagen@xs4all.nl>:
>>
>> 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)
> 
> 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
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2019-08-16  6:14 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <9BAE7219-2E4C-4B84-B0C3-C5F67D3FFCC2@fiee.net>
2019-08-15 21:06 ` Fwd: OSFONTDIR and Windows 10 Henning Hraban Ramm
2019-08-15 21:57   ` Hans Hagen
2019-08-16  5:40     ` OSFONTDIR Henning Hraban Ramm
2019-08-16  6:14       ` OSFONTDIR Hans Hagen

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).