<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>That's (I think) what we're talking about -- an 'anim' feature
tag to be added to the other registered feature tags. <br>
</p>
<p>Skef<br>
</p>
<div class="moz-cite-prefix">On 1/31/24 11:53, Behdad Esfahbod
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAF63+7X39h-RqB_E47ZpaUi5Y9fbbNcgT7-rEHjqOQ-Hb20pVA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div>On Wed, Jan 31, 2024 at 11:50 AM Skef Iterum <<a
href="mailto:skef@skef.org" moz-do-not-send="true"
class="moz-txt-link-freetext">skef@skef.org</a>> wrote:<br>
</div>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Sorry,
Davelab6, there's no issue for this one.<br>
<br>
I don't see the client as having any responsibilities for an
`anim` tag. <br>
It would indicate a good-, ideally best-, effort on the part
of the <br>
designer to work around aspects of the font that are
discontinuous from <br>
the perspective of animation.<br>
<br>
People are already animating variable fonts for video. The
mechanics of <br>
that on the client side are a separate issue.<br>
</blockquote>
<div><br>
</div>
<div>Maybe an `anim` GSUB/GPOS feature would be more
appropriate? People might want to animate the width, or the
weight, or other aspects of the font. Having an `anim` axis
only allows for animating one aspect of the font.</div>
<div><br>
</div>
<div>b</div>
<div><br>
</div>
<div> </div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Skef<br>
<br>
On 1/31/24 11:42, Laurence Penney wrote:<br>
> Remember that intermediate masters (including when
default is intermediate between min and max) disrupt smooth
animation, making G2 continuity impossible (even if the app
knows the intermediate axis values). That covers a large
proportion of variable fonts. Perhaps a font store or a
design tool could flag fonts without intermediates or
feature variations.<br>
><br>
> - Laurence<br>
><br>
>> On 31 Jan 2024, at 15:32, Behdad Esfahbod via
mpeg-otspec <<a href="mailto:mpeg-otspec@lists.aau.at"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">mpeg-otspec@lists.aau.at</a>>
wrote:<br>
>><br>
>> How would `anim` feature work? Would the client be
responsible to apply a (G1 / G2) continuous curve to it to
get the pulsating effect you want then? In other words, do
the min/max of the axis have to be the same or can be
different?<br>
>> behdad<br>
>> <a href="http://behdad.org/" rel="noreferrer"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">http://behdad.org/</a><br>
>><br>
>><br>
>> On Wed, Jan 31, 2024 at 1:45 AM Skef Iterum via
mpeg-otspec <<a href="mailto:mpeg-otspec@lists.aau.at"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">mpeg-otspec@lists.aau.at</a>>
wrote:<br>
>> This is another proposal idea I can't do properly
in the pre-April time<br>
>> frame, but it's short and simple.<br>
>><br>
>> Imagine you're a video editor working on a cable
commercial about a new<br>
>> way to Make Lots of Money!!! You overlay a row of
dollar signs from a<br>
>> cool variable display font and animate them to
"pulse" by changing their<br>
>> weight. Unfortunately, when you look at the result
the number of slashes<br>
>> in each dollar sign keeps changing, greatly
distracting your otherwise<br>
>> elegant and sophisticated effect.<br>
>><br>
>> The problem here is that doing the right thing for
a given position in<br>
>> design space isn't always the right thing for
animations that change the<br>
>> design space.<br>
>><br>
>> I think this distinction calls for a new registered
feature tag,<br>
>> probably 'anim', that when active avoids, undoes,
or compensates for any<br>
>> (or most) such abrupt adjustments. While this is
something that could<br>
>> always just be thrown onto 'ss15' or whatever, it
would be better to<br>
>> have a reserved name so that animation tools can
leave that tag turned<br>
>> on by default.<br>
>><br>
>> A registered feature tag would also indicate
something by its presence<br>
>> in a font: "we've thought about this problem".
Designers might even<br>
>> throw it into a font with no such adjustments just
to advertise that it<br>
>> is compatible with animation use.<br>
>><br>
>> This is a simple enough idea, but I lack the
context to come up with<br>
>> specifically what the section needs to say -- what
advice to give to<br>
>> designers. Someone closer to the design side of
things would do a better<br>
>> job. If anyone comes up with that wording but
doesn't want to worry<br>
>> about ISO header pages and such, send it to me and
I'll wrap it up into<br>
>> a proposal.<br>
>><br>
>> Thanks,<br>
>> Skef<br>
>><br>
>> _______________________________________________<br>
>> mpeg-otspec mailing list<br>
>> <a href="mailto:mpeg-otspec@lists.aau.at"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">mpeg-otspec@lists.aau.at</a><br>
>> <a
href="https://lists.aau.at/mailman/listinfo/mpeg-otspec"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a><br>
>> _______________________________________________<br>
>> mpeg-otspec mailing list<br>
>> <a href="mailto:mpeg-otspec@lists.aau.at"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">mpeg-otspec@lists.aau.at</a><br>
>> <a
href="https://lists.aau.at/mailman/listinfo/mpeg-otspec"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a><br>
</blockquote>
</div>
</div>
</blockquote>
</body>
</html>