ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Schmitz Thomas A." <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: MacOsX Mavericks and Luatex
Date: Thu, 24 Oct 2013 16:39:21 +0200	[thread overview]
Message-ID: <BFCFF01D-1A14-4217-A6A3-0D51657AD679@uni-bonn.de> (raw)
In-Reply-To: <52692BE9.7080804@wxs.nl>


On 24 Oct 2013, at 16:17, Hans Hagen <pragma@wxs.nl> wrote:

> Hm. The problem is that we get some oscillation (with a few year cycle) between the 'demand' for os fonts support vs tree only (as far as remember os font support was mostly requested by osx users). Anyhow, we can make it an option, but then the question is: what is the default (and who is going to defend that choice to distributers and users).
> 
> Hans

Yes, I’m aware that any default will make some users unhappy. I would prefer to have osfontdir unset by default because there’s a real speed penalty in having it set so I would agree with Alan on that one. (It would also abolish the inconsistency between platforms.) But for me the real question is: what do I have to do to have osfontdir unset as things are now? I tried some things, none worked. (see my earlier mail).

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


  parent reply	other threads:[~2013-10-24 14:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24  5:41 Pierre Bovet
2013-10-24  6:03 ` Schmitz Thomas A.
2013-10-24  7:01 ` Schmitz Thomas A.
2013-10-24  7:12   ` Schmitz Thomas A.
2013-10-24 14:17     ` Hans Hagen
2013-10-24 14:28       ` Alan BRASLAU
2013-10-24 14:39       ` Schmitz Thomas A. [this message]
2013-10-24 14:44         ` Aditya Mahajan
2013-10-24 22:01           ` Schmitz Thomas A.
2013-10-24 22:13             ` Hans Hagen
2013-10-24 22:33               ` Aditya Mahajan
2013-10-25  7:30               ` Meer, H. van der
2016-05-19 14:26               ` MacOsX OSFONTDIR environment variable Meer, Hans van der
2013-10-24 21:40         ` MacOsX Mavericks and Luatex Hans Hagen
2013-10-24  7:04 ` Wolfgang Schuster
2013-10-24  7:13   ` Schmitz Thomas A.
2013-10-24  7:24     ` Wolfgang Schuster
2013-10-24  7:30       ` Pierre Bovet
2013-10-24  7:36         ` Wolfgang Schuster
2013-10-24  7:45           ` Pierre Bovet
2013-10-24  8:00             ` Wolfgang Schuster
2013-10-24  8:08               ` Schmitz Thomas A.
2013-10-24  8:31                 ` Pierre Bovet
2013-10-24  9:56               ` Keith J. Schultz
2013-10-24 22:17                 ` Hans Hagen
2013-10-25  8:49               ` Taco Hoekwater
2013-10-25 13:01                 ` Otared Kavian
2013-10-24  9:13 ` Keith J. Schultz

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=BFCFF01D-1A14-4217-A6A3-0D51657AD679@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.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).