<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 1/24/24 23:47, Laurence Penney
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:B02B15FD-D72A-46DD-BC77-50D5729E47E9@lorp.org">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<blockquote type="cite">On 25 Jan 2024, at 01:25, Skef Iterum
via mpeg-otspec <a class="moz-txt-link-rfc2396E" href="mailto:mpeg-otspec@lists.aau.at"><mpeg-otspec@lists.aau.at></a> wrote:<br>
</blockquote>
<blockquote>There is a distinction between whether the text path
itself is skewed or<br>
rotated and whether a component in a composite is skewed or
rotated.<br>
Asking around it seems as though with the existing glyf
components<br>
instructions are <i>not</i> automatically turned off when
"compositing", but<br>
perhaps that info is wrong.
<p>Either way, though, that seems like something the
specification should<br>
clarify.</p>
</blockquote>
</div>
<div>I asked similar questions when I was getting my head around
TT hinting, and recall being told that skewed or rotated
components were not hinted. The person I asked would most likely
have been Greg Hitchcock.</div>
<div><br>
</div>
</blockquote>
Josh Hadley on our team got curious about this and did an experiment
or two<br>
in VTT. As far as we can tell there is no automatic disabling of
hints when using<br>
"not nice" transformations, at least in that tool. We can provide a
specific<br>
example or two if anyone needs them.<br>
<br>
It's possible that the "client side" implementations work
differently than the <br>
development tools but designers are likely to take the guidance of
those tools<br>
unless there is very strong conventional wisdom pointing in a
different<br>
direction.<br>
<p>Skef<br>
</p>
</body>
</html>