[gs-bugs] [Bug 698762] - MuPDF - Severely broken ePUB output when linked against FreeType's master branch

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698762

Bug ID: 698762
Summary: Severely broken ePUB output when linked against
FreeType's master branch
Product: MuPDF
Version: master
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: major
Priority: P4
Component: epub
Assignee: mupdf-***@artifex.com
Reporter: ***@gmail.com
QA Contact: gs-***@ghostscript.com
Word Size: ---

Created attachment 14470
--> http://bugs.ghostscript.com/attachment.cgi?id=14470&action=edit
Test document

The pixmap generated for the first page of `test.epub` is:
- `output-2.8.1.png` when linked against FreeType 2.8.1.
- `output-954710dd.png` when linked against FreeType's master branch at commit
954710dd.

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698762

--- Comment #1 from Bastien Dejean <***@gmail.com> ---
Created attachment 14471
--> http://bugs.ghostscript.com/attachment.cgi?id=14471&action=edit
Output for FreeType 2.8.1

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698762

--- Comment #2 from Bastien Dejean <***@gmail.com> ---
Created attachment 14472
--> http://bugs.ghostscript.com/attachment.cgi?id=14472&action=edit
Output for FreeType's master at 954710dd

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698762

Tor Andersson <***@artifex.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@artifex.com

--- Comment #3 from Tor Andersson <***@artifex.com> ---
Building against freetype 2.8.1 works for me. Did you compile with the freetype
2.8.1 headers, or did you compile with one version of the headers and link
against another version of the library?

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698762

--- Comment #4 from Bastien Dejean <***@gmail.com> ---
(In reply to Tor Andersson from comment #3)

Post by b***@artifex.com
Building against freetype 2.8.1 works for me. Did you compile with the
freetype 2.8.1 headers, or did you compile with one version of the headers
and link against another version of the library?

I'm sorry if I haven't been clear. The output is indeed correct when linked
against FreeType 2.8.1: the problem only occurs with FreeType's master branch.

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698762

--- Comment #5 from Tor Andersson <***@artifex.com> ---
Sorry, it's monday and I misunderstood!

I can reproduce the problem with freetype's master, and have tracked it down to
a bug in freetype. You should report it with them.

The problem in freetype originates with commit
0589e3c01212fc77470ddde13d379a16170af151
Author: Ewald Hew <***@gmail.com>
Date: Mon Sep 25 06:10:20 2017 +0200

Use the new objects.

* include/freetype/internal/psaux.h, src/psaux/psauxmod.c: Fix
switching between new and old engines.

* src/cff/cffgload.c, src/cff/cffparse.c: Update calls.

* src/psaux/psblues.c, src/psaux/psfont.c, src/psaux/psfont.h,
src/psaux/psft.c, src/psaux/psft.h, src/psaux/psintrp.c: Update all
to use new objects.

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698762

--- Comment #6 from Tor Andersson <***@artifex.com> ---
I have submitted bugs upstream.

Please do not use FreeType versions newer than 2.8 until these have been fixed.

https://savannah.nongnu.org/bugs/index.php?52466
https://savannah.nongnu.org/bugs/index.php?52467