ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: MacOsX Mavericks and Luatex
Date: Fri, 25 Oct 2013 21:01:33 +0800	[thread overview]
Message-ID: <F04B8DA2-B326-42A0-A9AD-4973431E93EF@gmail.com> (raw)
In-Reply-To: <526A307F.60009@elvenkind.com>

Hi everyone,

I installed MacOS X 10.9 « Mavericks » on top of the latest MacOS X 10.8, and could run my installation of ConTeXt stand alone without any problem, despite having Skia.ttf on my system:

	Version	8.0d1e1
	Location	/Library/Fonts/Skia.ttf
	Unique name	Skia Regular; 8.0d1e1; 2012-09-05
	Copyright	© 1993-2002 Apple Inc.
	Enabled	Yes
	Duplicate	No
	Copy protected	No
	Glyph count	591

The rights for this font are:

	-rw-r--r--  1 root  wheel   480K 25 oct 04:56 Skia.ttf

(these rights are the same as other fonts, and clearly I never changed these…).
I also made anew the formats after having installed Mavericks, and did not notice any problem with a dozen tests I did.
So it seems that the cases in which problems have shown up are quite various.
The version of ConTeXt I have now is ConTeXt  ver: 2013.10.15 13:52 MKIV beta  fmt: 2013.10.25

(By the way, even after running first-setup.sh, I get always the same version… This may be due to the fact that I am in China right now?).

A last word regarding the requests for changing the defaults for system fonts.
The present situation has the advantage that people who are far from being geeks (for instance like me and the secretaries to whom I have shown how to use ConTeXt) can use whatever fonts they have on their system without tweaking the .cnf file, and without knowing how to write a typescript (thanks to the features added recently by Wolfgang). 
People who have the  technical knowledge and don’t want to use their system fonts because of waste of typesetting time, can indeed change this default behaviour.
So PLEASE don’t change the present default!

Best regards: OK


On 25 oct. 2013, at 16:49, Taco Hoekwater <taco@elvenkind.com> wrote:

> On 10/24/2013 10:00 AM, Wolfgang Schuster wrote:
>> 
>> Am 24.10.2013 um 09:45 schrieb Pierre Bovet <pierre67@me.com>:
>> 
>>> OK, that was not a good example…
>>> But the the message above is coming with any other otf fonts:
>>> 
>>> fonts           > names > globbing path '/Library/Fonts/**.ttf'
>>> 
>>> mtx-context     | fatal error: no return code, message: luatex: execution interrupted
>> 
>> Can you remove the Skia.ttf (copy it to another directory) font from /Library/Fonts,
>> this helped on my system to get rid of the error message.
> 
> It is definitely Skia.ttf itself, and not its permissions. After my
> upgrade to Mavericks, I got a fresh Skia.ttf (491796 bytes), and even
> though the permissions were fine (644), it crashes luatex, standalone
> fontforge, and ttx.
> 
> Actually, changing the file permissions to 000 (not readable by anyone)
> fixed context's use of system fonts.
> 
> ttx says: TT instructions error: 'illegal opcode: 0x91'; texlua and
> fontforge just crash on an undefined glyph in the internals of the font.
> 
> Best wishes,
> Taco
> 
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

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


  reply	other threads:[~2013-10-25 13:01 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.
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 [this message]
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=F04B8DA2-B326-42A0-A9AD-4973431E93EF@gmail.com \
    --to=otared@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).