Re: Re: fc-glyphname bug

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


Another two font families which may cause fc-cache to fail (this time
with a segv) but work with the changes I suggested are those in:


More precisely, gentoo sticks both of those in /usr/share/fonts/OTF
(and only those) and one or more of the fonts therein caused the SEGV.

With the change to FC_GLYPHNAME_MAXLEN and the full set of glyphnames
that dir now caches correctly, again.

I presume this is due to some change in freetype, since it all of
course used to work.  But now if fc tries to get the glyph names
from a font and specifies a max lenght too short it either dies
or goes into an infinite loop, and since it uses FC_GLYPHNAME_MAXLEN
as the max length in that function call, either that needs to be
large enough to cover any glyph name or another constant is needed
for use in FcFreeTypeCharSetAndSpacing().

James Cloos <cloos@xxxxxxxxxxx>         OpenPGP: 1024D/ED7DAEA6
Fontconfig mailing list

[Index of Archives]     [Fedora Fonts]     [Fedora Users]     [Fedora Cloud]     [Kernel]     [Fedora Packaging]     [Fedora Desktop]     [PAM]     [Gimp Graphics Editor]     [Yosemite News]

  Powered by Linux