[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ft-devel] Can freetype be more tolerant with this font?

From: Albert Astals Cid
Subject: [ft-devel] Can freetype be more tolerant with this font?
Date: Sun, 23 Dec 2018 13:36:49 +0100

Hi, if try to render this pdf file
with poppler you'll see it's missing an m

I can "fix" it with this patch

diff --git a/src/base/ftoutln.c b/src/base/ftoutln.c
index f54ebdf5c..48b351db2 100644
--- a/src/base/ftoutln.c
+++ b/src/base/ftoutln.c
@@ -221,8 +221,7 @@
             FT_Vector  vec1, vec2;
-            if ( point + 1 > limit                             ||
-                 FT_CURVE_TAG( tags[1] ) != FT_CURVE_TAG_CUBIC )
+            if ( point + 1 > limit )
               goto Invalid_Outline;
             point += 2;

As shown in

I obviously have no idea how important the check for FT_CURVE_TAG_CUBIC is, 
just that for this particular font removing it makes it work.

I'm attaching the extracted font out of the pdf file.

fontforge seems to open it "just fine", though when asked to check errors on 
the paths of 'm' it gives some, but given i'm a total font/fontforge newbie i'm 
not sure how important those are.

Do you think there's a way that freetype can "render" that m? Or should we just 
tell the font authors to fix it?


Attachment: CAAAAA+LinuxBiolinumOItalic
Description: application/font-type1

reply via email to

[Prev in Thread] Current Thread [Next in Thread]