<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> <span class="fn">V Stuart Foote</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - Replacing Source Sans Pro by Source Sans Variable"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=114855">bug 114855</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Keywords</td>
<td>needsUXEval
</td>
<td>
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>libreoffice-ux-advise@lists.freedesktop.org
</td>
<td>khaledhosny@eglug.org, michael.meeks@collabora.com, quikee@gmail.com, vstuart.foote@utsa.edu
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>DUPLICATE
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - Replacing Source Sans Pro by Source Sans Variable"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=114855#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - Replacing Source Sans Pro by Source Sans Variable"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=114855">bug 114855</a>
from <span class="vcard"><a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> <span class="fn">V Stuart Foote</span></a>
</span></b>
<pre>There is no internal UI for working with OpenType 1.8 OTF Variable fonts. Work
flows would need to be altered as would printing and export.
Why would we change over to Source Sans Variable now? Absent correct handling
of the variable font--we would get an arbitrary and likely unusable rendering
of the font--or more likely a fall-back to another on system font. We'd just be
wasting space in the deployment package.
Until such time as support for OTF 1.8.2 "fvar" (<a class="bz_bug_link
bz_status_NEW "
title="NEW - Support OpenType Font Variation based text layout"
href="show_bug.cgi?id=103596">bug 103596</a>) is implemented
substituting this or any other variable font makes no sense.
Duping this to <a class="bz_bug_link
bz_status_NEW "
title="NEW - Support OpenType Font Variation based text layout"
href="show_bug.cgi?id=103596">bug 103596</a>, as only when that enhancement is undertaken would it
make sense to adopt any variable font.
*** This bug has been marked as a duplicate of <a class="bz_bug_link
bz_status_NEW "
title="NEW - Dropbox support for LO Remote Files"
href="show_bug.cgi?id=103506">bug 103506</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>