Re: [ft-devel] New FreeType release within a week

> I think this may be a result of an implementation choice for > combining T1 and CFF. There is no limit to the number of hints that > can occur in a Type1 charstring. Each time there is a hint > substitution, previously used hints are discarded. On the other > hand, CFF requires that all

Re: [ft-devel] New FreeType release within a week

> Set blend coordinates, then get design coordinates and observe that > they reflect the default instance. Got it, thanks. Should be fixed now in git, please test! Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org

Re: [ft-devel] New FreeType release within a week

I think this may be a result of an implementation choice for combining T1 and CFF. There is no limit to the number of hints that can occur in a Type1 charstring. Each time there is a hint substitution, previously used hints are discarded. On the other hand, CFF requires that all hints be

Re: [ft-devel] New FreeType release within a week

>>> The largest number of hints is 4111 (!). > > WL> Ouch! > > That glyph (uni2591) is an offset array of 16x16 circles. > > Not hinting that one would certainly be fine. > > (U+2591 is LIGHT SHADE.) Indeed. And the next glyph in this font gets heavily distorted with the old Type 1

Re: [ft-devel] Building in a custom directory

> Why when building in a custom directory, the headers are located in > sub directories? These cannot be found by other linkers. > > https://stackoverflow.com/questions/45627349/building-freetype2-in-a-custom-directory-which-must-be-found-when-building-gd After installation of FreeType there

Re: [ft-devel] New FreeType release within a week

>> The largest number of hints is 4111 (!). WL> Ouch! That glyph (uni2591) is an offset array of 16x16 circles. Not hinting that one would certainly be fine. (U+2591 is LIGHT SHADE.) -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6

[ft-devel] Building in a custom directory

Hello, Why when building in a custom directory, the headers are located in sub directories ? These cannot be found by other linkers. https://stackoverflow.com/questions/45627349/building-freetype2-in-a-custom-directory-which-must-be-found-when-building-gd Kind Regards, Stephane Eybert * *

Re: [ft-devel] New FreeType release within a week

>> I'm wondering, how about leaving the CFF limit as is and apply it >> to Type1, too, and just turn off hinting for that glyph? Not >> entirely correct, but an easy way out when the hinting obviously >> went wrong. > > Actually, since the FreeType hinter handles it fine, how about > returning

Re: [ft-devel] New FreeType release within a week

> I'm wondering, how about leaving the CFF limit as is and apply it to Type1, > too, and just turn off hinting for that glyph? Not entirely correct, but an > easy way out when the hinting obviously went wrong. Actually, since the FreeType hinter handles it fine, how about returning a specific

Re: [ft-devel] New FreeType release within a week

I'm wondering, how about leaving the CFF limit as is and apply it to Type1, too, and just turn off hinting for that glyph? Not entirely correct, but an easy way out when the hinting obviously went wrong. ___ Freetype-devel mailing list

Re: [ft-devel] New FreeType release within a week

On Sat, Dec 30, 2017 at 1:41 PM, Werner LEMBERG wrote: > > Folks, > > > I want to make a new FreeType release within a week, if possible. > Some issues. > > . Behdad, please provide a problematic example w.r.t. conversion of > design to blend coordinates. > Set blend

Re: [ft-devel] New FreeType release within a week

> The largest number of hints is 4111 (!). Ouch! > Attached is the output for all fonts still with rejected glyphs. Thanks. > It's definitely not practical to increase the limit so much; I'm > thinking that this is good enough for now. OK. It would be nice if FreeType switched to unhinted

Re: [ft-devel] New FreeType release within a week

> Yes, sounds sensible, thanks. Could you do a sweep over all Type 1 > fonts from TeXLive just to be sure? I guess this is the most > important repository of PFB files that is still in use. After increasing the limit to 360, out of 6802 fonts tested in TeXLive, 53 fonts still failed, down from

Re: [ft-devel] Announcing ttfautohint 1.8

> PPS: Due to a bug in another package (which I can't control), Homebrew > support is not yet available, cf. > >https://github.com/Homebrew/homebrew-core/pull/22321 This has just been fixed, so the new version has also landed in Homebrew. Werner