<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Subfamilies with different OpenType 'size' should not be merged" href="https://bugs.freedesktop.org/show_bug.cgi?id=95428#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Subfamilies with different OpenType 'size' should not be merged" href="https://bugs.freedesktop.org/show_bug.cgi?id=95428">bug 95428</a> from <a class="email" href="mailto:akira@tagoh.org" title="Akira TAGOH <akira@tagoh.org>"> Akira TAGOH</a> <pre>(In reply to gm from <a href="show_bug.cgi?id=95428#c6">comment #6</a>) > Hello, is there any update regarding my suggestion to disregard name IDs 16 > & 17 when dealing with optical fonts? Thank you! Sorry, still don't have a time to take a look carefully. Though storing the optical font name into the new object may be an idea, but it comes to mind why font developers adds the same (sub-)family names to the different typefaces. I guess they expect to access them with it seamlessly. then it may be relevant to <a class="bz_bug_link bz_status_NEW " title="NEW - Font subfamilies merged" href="show_bug.cgi?id=13416">https://bugs.freedesktop.org/show_bug.cgi?id=13416</a>. though your suggestions looks opposed to it. For the functionality of fontconfig, to get much better fonts, more conditions needs to be given right. otherwise the result may be vague and not expected one for someone. in that sense, IMHO supporting the 'size' feature in OpenType may be a solution for this issue perhaps - of course applications needs to request the proper things to polish the result. otherwise it may not needs to be fontconfig. applications could read a font directly or the primitive way. I'll revisit this issue once I have a time. but just for the record at this moment.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>