On Sep 1, 2016, at 10:53 , Andreas Falkenhahn <[email protected]> wrote: > > Who said that the answer was clearly "no”?
Me. And you. You took a trivially simple single-character example, and failed to come up with the same answer. > So far these attempts haven’t been successful but … You *might* find a combination of settings that brings success in your test cases, but that’s just fixing the test when you know the answer. > When rendering the text using ATSUDrawText() > and CTLineDraw(), the pixels match *exactly*. There is not a single > difference, > it is exactly the same, pixel by pixel. It’s hardly surprising this would be true some, even most, of the time. But are you sure that there was no bug or deficiency in ATSUI code that Apple fixed in CoreText? No bug in font file metrics or font hinting that has been fixed in 10 years of font updates? > That's why I am of the opinion that > it should also be possible to achieve an identical look when drawing strings > glyph by glyph and manually calculating the advance. No, absolutely not, and that’s my real point. Line layout *uses* individual glyph advance widths, but the effective advance width of glyphs within in a line of text is contextually dependent, computed using other factors, some of which are in practical terms not predictable. _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
