<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [FreeType] Incorrect application of glyph positioning in the Y direction"
href="https://bugs.webkit.org/show_bug.cgi?id=161493#c17">Comment # 17</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [FreeType] Incorrect application of glyph positioning in the Y direction"
href="https://bugs.webkit.org/show_bug.cgi?id=161493">bug 161493</a>
from <span class="vcard"><a class="email" href="mailto:mmaxfield@apple.com" title="Myles C. Maxfield <mmaxfield@apple.com>"> <span class="fn">Myles C. Maxfield</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=161493#c11">comment #11</a>)
<span class="quote">> GlyphBuffer is only used for painting. As such, we can save space if,
> instead of storing separate advances / origins in it, we collapse these into
> "painting advances" which are the offset from each glyph's paint position to
> the next.
>
> I considered renaming GlyphBuffer to something like PaintingGlyphBuffer but
> ultimately decided it wasn't worth the effort.
>
> Ultimately, we should remove the m_offsets member from GlyphBuffer in the
> Windows port. I plan on doing this at some point in the future. Rather than
> increasing the usage of this variable, I would suggest computing each
> glyph's paint position inside HarfBuzzShaper (thereby taking into account
> the offsets) and storing that in GlyphBuffer.</span >
I'm doing this at <a class="bz_bug_link
bz_status_NEW "
title="NEW - Remove unused member of GlyphBuffer"
href="show_bug.cgi?id=161814">https://bugs.webkit.org/show_bug.cgi?id=161814</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>