<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Installation: does not use latest font version, and replaces with bundled-older" href="https://bugs.documentfoundation.org/show_bug.cgi?id=111330#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Installation: does not use latest font version, and replaces with bundled-older" href="https://bugs.documentfoundation.org/show_bug.cgi?id=111330">bug 111330</a> from <a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> Mike Kaganski</a> <pre>I'm not sure I understand the problem correctly. The description is vague. As far as I know, 5.4.0.3 bundled 2.030 version of SourceCodePro fonts. So, it's unclear how could it downgrade to 2.010. Also, at least for these fonts, it's improbable that LibreOffice would do all this, because it actually does contain fonts versions in MSI, and unless its records are wrong and report values greater than actual (which isn't the case for these fonts), it should do the job right. Just FYI: we don't bundle PT Serif anymore as of 6.0. The commit <a href="https://cgit.freedesktop.org/libreoffice/core/commit/?id=c91f70f9b0129685737260c04a2e347726f1dedf">https://cgit.freedesktop.org/libreoffice/core/commit/?id=c91f70f9b0129685737260c04a2e347726f1dedf</a> should take care of the cases where our MSI database contained wrong version records; but as I said, this was not the case for these fonts.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>