[cairo] Fwd: Cairo 1.14 error on OS X 10.10.3 Yosemite

suzuki toshiya mpsuzuki at hiroshima-u.ac.jp
Sat May 9 21:35:21 PDT 2015


Although I've not tested for the reproduction of the issue,
the problem you reported reminds me a regression in 1.14.2
which is resolved in the latest git head (fixed on 2015-04-24).
The discussion is here (see the message posted on 2015-03-16,
from Inkscape developer).
Unfortunately, there are no screenshots, I don't know how
the regression appear on the Inkscape.

Could you try the latest git head to assure if it is yet
another regression?


suzuki toshiya wrote:
> Hi,
> Because there was a discussion whether an obsolete Mac OS X
> function to extract an outline data from a glyph in font
> should be kept (to support legacy platform) or replaced by
> newer function (for better maintenancability), I'm much
> interested in this issue (although my hands are very slow).
> I want to try to reproduce the problem. Could you post the
> SVG that you used?
> Regards,
> mpsuzuki
> Daven Quinn wrote:
>> Hello,
>> I recently upgraded to Cairo 1.14.2 (installed via Homebrew) on my Mac 
>> OS X
>> (latest) system. I am using it via CairoSVG to create PDF graphics. The
>> upgrade broke the glyph rendering of CairoSVG, resulting in grossly
>> too-large font glyphs (with the same baseline/spacing as prior, 
>> leading to
>> compressed text). I have tried building from source and relinking. An
>> example of the output is shown below.
>> Downgrading to cairo 1.12.16 fixes the issue (see attached), although the
>> following warning is raised (which does not appear in 1.14):
>> May  4 18:37:47 Daven-Quinn python2.7[993] <Error>: The function
>> ‘CGFontGetGlyphPaths’ is obsolete and will be removed in an upcoming
>> update. Unfortunately, this application, or a library it uses, is using
>> this obsolete function, and is thereby contributing to an overall
>> degradation of system performance.
>> Any insights on a possible fix?
>> Daven
>> note: I tried sending with the below-linked files as attachments, but it
>> was over the 150 kB (!) limit for message size, so I'm not sure if the
>> email got through. A graphics library should accept issues in graphical
>> form! It seems like source-control should be migrated to a newer platform
>> to ease community contributions.
>>>>  cairo-1.14.pdf
>> <https://docs.google.com/a/davenquinn.com/file/d/0BzFTyjxorIWAZ042NUJzVGNEZl8waktVRXpZRWZLaVZuVEJN/edit?usp=drive_web> 
>> ​​
>>  cairo-1.12.pdf
>> <https://docs.google.com/a/davenquinn.com/file/d/0BzFTyjxorIWAYnExd2JfQWU3ZzZSdjBDU3VDa21WOExfOC0w/edit?usp=drive_web> 

More information about the cairo mailing list