<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Make it more obvious that a font has been substituted (see comment 12)"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=96872#c20">Comment # 20</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Make it more obvious that a font has been substituted (see comment 12)"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=96872">bug 96872</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>(In reply to Heiko Tietze from <a href="show_bug.cgi?id=96872#c19">comment #19</a>)
<span class="quote">> Proposal has been mad in this blog post
> <a href="https://design.blog.documentfoundation.org/2018/02/18/improvements-font">https://design.blog.documentfoundation.org/2018/02/18/improvements-font</a>-
> listing/.
>
> Removing UX to attract devs.</span >
Actually that was the font listing portion, improving the font
fallback/substitution was this blog (and <a class="bz_bug_link
bz_status_NEW "
title="NEW - Font substitution mechanism for import formats"
href="show_bug.cgi?id=104667">bug 104667</a>)
<a href="https://design.blog.documentfoundation.org/2016/10/21/dealing-with-missing-fonts/">https://design.blog.documentfoundation.org/2016/10/21/dealing-with-missing-fonts/</a>
But that is ready to move forward with dev effort as well...</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>