<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - MS Gothic and MS Mincho text rendered differently at different zoom levels and claimed to be substituted" href="https://bugs.documentfoundation.org/show_bug.cgi?id=107462#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - MS Gothic and MS Mincho text rendered differently at different zoom levels and claimed to be substituted" href="https://bugs.documentfoundation.org/show_bug.cgi?id=107462">bug 107462</a> from <a class="email" href="mailto:khaledhosny@eglug.org" title="Khaled Hosny <khaledhosny@eglug.org>"> Khaled Hosny</a> <pre>The different rendering is properly is how the fonts are set up in the “gasp” table which specifies the anti-aliasing behavior for given pixel sizes. CJK fonts typically prefer string hinting and no anti-aliasing at smaller pixel sizes. Anyway, I think it is just DirectWrite doing its magic since I don’t recall us fiddling with anti-aliasing settings. Not displaying the English name if the font do not have a localized name for the current locale is an independent issue and should be reported separately. Marking the font as being substituted when localized name is used in a different locale is also an independent issue and should be reported separately.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>