<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Support enabling optional smart font features"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=58941#c76">Comment # 76</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Support enabling optional smart font features"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=58941">bug 58941</a>
from <span class="vcard"><a class="email" href="mailto:libretraining.tutorials@gmail.com" title="LibreTraining <libretraining.tutorials@gmail.com>"> <span class="fn">LibreTraining</span></a>
</span></b>
<pre>Created <span class=""><a href="http://bugs.documentfoundation.org/attachment.cgi?id=141006" name="attach_141006" title="QuarkXpress OpenType interface examples">attachment 141006</a> <a href="http://bugs.documentfoundation.org/attachment.cgi?id=141006&action=edit" title="QuarkXpress OpenType interface examples">[details]</a></span>
QuarkXpress OpenType interface examples
The best interface I have seen for OpenType support is in QuarkXpress.
The OpenType features are usually hidden and are accessed from a spinner.
The application actually reads the font file and only activates the available
features.
Unavailable features are grayed-out.
So the user knows what is available.
This image shows examples for Liberation Sans and Minion Pro.</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>