Re: [ft-devel] TTFAutohint Without TT Point Numbers

Things like "point #gre356hlue3752hlye" or "point that is located at x=36.87% y=78.56% of the glyph bbox" On Di., 12. Apr. 2016 at 07:41, Werner LEMBERG wrote: > > > I've had situations where I relied on glyph names but I had those > > where I relied on glyph ids (numbers) and it

Re: [ft-devel] TTFAutohint Without TT Point Numbers

> I've had situations where I relied on glyph names but I had those > where I relied on glyph ids (numbers) and it was a superior choice. > If I have 1239 glyphs in one font and 1239 glyphs in another, > chances that the glyph IDs are consistent are actually high. I only > need to check what's

Re: [ft-devel] TTFAutohint Without TT Point Numbers

In other words, computational checking that something "has gone wrong" between two versions of a font is easier if your system relies on point numbers. If it relies on some more abstract data (like point names), chances of horrible things happening and going undetected are actually higher. :)

Re: [ft-devel] TTFAutohint Without TT Point Numbers

I agree with Werner. There are concepts like point names or UIDs in UFO but by themselves they're not really anymore robust than point numbers. Software that deals with point names/UIDs needs to keep them (make sure they don't get lost), and it's actually the same as making sure you keep