I have no idea what you're talking about. Please, clarify what this difference is supposed to be, otherwise this is just spreading rumors.
On Wed, Jul 5, 2023 at 2:33 PM Hin-Tak Leung <ht...@users.sourceforge.net> wrote: > > > On Wednesday, 5 July 2023 at 20:49:42 GMT+8, Hin-Tak Leung < > ht...@users.sourceforge.net> wrote: > > > > On Wednesday, 5 July 2023 at 03:24:11 GMT+8, Cosimo Lupo < > cos...@anthrotype.com> wrote: > > > > Hin-Tak, what do you mean by "Google OT-SVG fonts"? They're only one > OT-SVG format. > > > Yes and no. I don't have that many OT-SVG fonts - 3 from Adobe/Mozilla > sources, and the rest (more than 2 and less than 10) from Google Fonts. The > two sets behave differently, and get processed by two different code paths > in freetype2-demos. The Google set triggers the memory exhaustion bug I > fixed in freetype2-demos about a month ago; the Adobe/Mozilla set does not. > > > That was all part of the activities around the time with the Google font > SVG subsetting bug. Look at the freetype2-demo log around the same time you > investigated and fixed the subletting bug. > > Actually having looked at Skia and skia-python's SVG related functionality > last night, Skia also follows two slightly different code paths for the two > "types" of OT-SVG fonts. There will be a small "if x else ..." clause > separating the two in Skia related code, if /when I finish. > > >
