View Issue Details

IDProjectCategoryView StatusLast Update
0000924luatexluatex bugpublic2015-10-22 10:11
Reporterjpintar Assigned ToHans Hagen  
PrioritylowSeveritycrashReproducibilityalways
Status closedResolutionfixed 
PlatformIntel Core i5OSMicrosoft WindowsOS Version8.1 x64
Product Version0.79.1 
Summary0000924: Invalid character leads to fatal error
DescriptionDocuments using the proprietary font AmorSerifTextPro.otf from the Storm Type Foundry (https://www.stormtype.com/families/amor-serif) fail to compile with LuaTeX and ConTeXt, with the following error message:

!LuaTeX error (file AmorSerifTextPro.otf): Invalid character.
 ==> Fatal error occurred, no output PDF file produced!

The problem does not arise with XeTeX, or with any other fonts in the same family.
Steps To ReproduceLuaTeX:

    \input luaotfload.sty
    \font\amor=file:AmorSerifTextPro.otf\amor
    Sphinx of black quartz, judge my vow. 1234567890
    \bye

ConTeXt:

    \starttext
      \definedfont[file:AmorSerifTextPro.otf at 12pt]
      Sphinx of black quartz, judge my vow. 1234567890
    \stoptext

The following compiles in XeTeX without error:

    \font\amor="[AmorSerifTextPro.otf]"\amor
    Sphinx of black quartz, judge my vow. 1234567890
    \bye
Additional Information1. There seem to be no obvious problems with the font file. It can be dumped to TTX as well as opened in FontForge without any complaints.

2. If the font is converted to TrueType using FontForge, the compilation proceeds without error.

3. The error seems to occur when writing to PDF, rather than during loading, since the following script runs with texlua without error:

    #!/usr/bin/env texlua
    local fnt = fontloader.open "./AmorSerifTextPro.otf"
    local tbl = fontloader.to_table (fnt)
    fontloader.close(fnt)

4. Also discussed at https://github.com/lualatex/luaotfload/issues/264
TagsNo tags attached.

Activities

Hans Hagen

2015-02-16 12:10

manager   ~0001317

it's a commercial font so you need to donate / arrange a legal copy to get it solved

jpintar

2015-02-18 09:30

reporter   ~0001318

OK. I'll send you an email.

Hans Hagen

2015-10-22 10:11

manager   ~0001464

if this problem is still there, i need to have the font; also as it relates to context best report it on the context list then

Issue History

Date Modified Username Field Change
2015-02-16 04:46 jpintar New Issue
2015-02-16 12:10 Hans Hagen Note Added: 0001317
2015-02-18 09:30 jpintar Note Added: 0001318
2015-03-21 15:06 Hans Hagen Assigned To => Hans Hagen
2015-03-21 15:06 Hans Hagen Status new => assigned
2015-10-22 10:11 Hans Hagen Note Added: 0001464
2015-10-22 10:11 Hans Hagen Status assigned => closed
2015-10-22 10:11 Hans Hagen Resolution open => fixed