From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: OSFONTDIR
Date: Thu, 3 Jun 2010 16:50:59 +0200 [thread overview]
Message-ID: <AANLkTinlNS1dceYEnYa2xmBev_r3y0wE017g-8-766jC@mail.gmail.com> (raw)
Dear Hans,
Some time ago the following code was working. On Mac it seems to have
no influence now (OSFONTDIR doesn't get "fixed"), but if I set it in
environment to the same string, it works.
local function check_configuration() -- not yet ok, no time for debugging now
if os.env["OSFONTDIR"] then
-- ok
elseif os.type == "windows" then
os.setenv("OSFONTDIR","c:/windows/fonts//")
elseif os.type == "macosx" then
os.setenv("OSFONTDIR","$HOME/Library/Fonts//;/Library/Fonts//;/System/Library/Fonts//")
end
end
Can it be that setenv doesn't really set anything (it just sets it
locally to some variable) and then resolvers only look for proper
environmental or texmf.cnf variables?
I have an impression that that function has been removed from LuaTeX a
while ago, but I may be wrong.
Mojca
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2010-06-03 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 14:50 Mojca Miklavec [this message]
[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
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=AANLkTinlNS1dceYEnYa2xmBev_r3y0wE017g-8-766jC@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--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).