From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: MacOsX Mavericks and Luatex
Date: Fri, 25 Oct 2013 10:49:03 +0200 [thread overview]
Message-ID: <526A307F.60009@elvenkind.com> (raw)
In-Reply-To: <7C8D60AB-7AD9-4B1D-ADE5-A50EE0036160@gmail.com>
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-10-25 8:49 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 [this message]
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=526A307F.60009@elvenkind.com \
--to=taco@elvenkind.com \
--cc=ntg-context@ntg.nl \
--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).