<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Incorrect handling of font families (weight, style, stretches) on Mac" href="https://bugs.documentfoundation.org/show_bug.cgi?id=69254#c81">Comment # 81</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Incorrect handling of font families (weight, style, stretches) on Mac" href="https://bugs.documentfoundation.org/show_bug.cgi?id=69254">bug 69254</a> from <a class="email" href="mailto:thlinard@gmail.com" title="Thomas Linard <thlinard@gmail.com>"> Thomas Linard</a> <pre>(In reply to LibreTraining from <a href="show_bug.cgi?id=69254#c80">comment #80</a>) > I think part of the problem is these are not looked at together. > Some of the problems appear to be font defects. > Some of the problems may be the font meta data, or lack thereof. If you think fonts have bugs, please report them to their creator (it can actually happen, but it's rare, and if the tricks around the nameID 1 & 2 that were used 15 years ago to get around the problems beyond RIBBI are no longer those in favor today, it doesn't matter, as long as the nameID 4, 6, 16 and 17, possibly 21 and 22, are correct). > Until Windows, Mac, and Linux testers are testing the same font families, > and those font families are determined to not have bugs or have been fixed, > and comparing what works and what does not work by platform, > this is just a scattershot approach. > > Bundled fonts may be "corrected/enhanced* and some issues may go away. Most of the time, proprietary licenses for fonts doesn't allow modification (and never, ever, distribution of modified fonts). So you've to deal with the fonts in the state they're in.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>