ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan Braslau via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>,
	Alan Braslau <alan.braslau@icloud.com>
Subject: [NTG-context] Re: OSFONTDIR
Date: Fri, 21 Jul 2023 16:48:41 +0200	[thread overview]
Message-ID: <309b3930-886d-1de3-3719-09c04bf1acf9@icloud.com> (raw)
In-Reply-To: <0626f426-321d-e274-a0ff-177a90b49163@icloud.com>

Thomas,

I actually set OSFONTDIR=.
which seems to be a sane default. I store specific font files with 
projects (along with a copy of the ConTeXt distribution used to typeset 
the project). This way, I can come back to a project later and make 
minor corrections without running into surprises or the need to update 
my sources.

Alan



On 21/07/23 21/07/23, 16:43, Alan Braslau wrote:
> On 19/07/23 19/07/23, 22:51, Hans Hagen via ntg-context wrote:
>>> is looking for system fonts by default the new standard? Is it a good 
>>> idea?
>>>
>>> Thank you and all best
>> it is a tex live thing; you can just set that variable to nothing, in 
>> the environment or in a local file like in
>>
>> ../tex/texmf-local/web2c/texmfcnf.lua
>>
>> normally texmf-fonts is where i put fonts and that one should win
> 
> A TeX-live thing can be the default for TeX live.
> 
> I agree with Thomas, not explicitly including the system fonts by 
> default is preferable. Maybe the standalone installation still does this 
> - I hope so - but have not checked. If it defauts to including the 
> system fonts, I would suggest that this is not necessarily a good idea.
> 
> Alan
> 

-- 
Alan Braslau
816 West Mountain Avenue
Fort Collins, CO 80521 USA
mobile: (970) 237-0957

Conserve energy! ;-)

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2023-07-21 14:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19 20:27 [NTG-context] OSFONTDIR Thomas A. Schmitz
2023-07-19 20:51 ` [NTG-context] OSFONTDIR Hans Hagen via ntg-context
2023-07-20 17:44   ` Pablo Rodriguez
2023-07-21 14:43   ` Alan Braslau via ntg-context
2023-07-21 14:48     ` Alan Braslau via ntg-context [this message]

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=309b3930-886d-1de3-3719-09c04bf1acf9@icloud.com \
    --to=ntg-context@ntg.nl \
    --cc=alan.braslau@icloud.com \
    --cc=thomas.schmitz@uni-bonn.de \
    /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).