Description: does not use latest font version e.g. https://github.com/adobe-fonts/source-code-pro/releases (2.030) vs 2.010,noitalics http://www.paratype.com:80/uni/public/PTSerif.zip (1.002 2014) vs 1.000 does not check if later version already installed, and replaces with bundled older also reverting-to-later font versions in windows not smooth (file-name-conflict due to replaced-later font-file not removed-internally but de-registered) Steps to Reproduce: 1. note fonts already installed and their versions in control panel, also record command prompt C:\Windows\Fonts "dir" 2. update or install libreoffice 3. compare installed fonts after installation Actual Results: source-code pro is reverted with older version, cmd.exe dir reveals both older and nwer files in folder but only the bunded-libreoffice-version in registered/installed Expected Results: uses latest versions of the free fonts and use scripts to auto-check-for-updates, if later version already installed (check file version, dates, metadata, size?) dont replace Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
For the test, could you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#Windows) and give a new try? Indeed, I don't think fonts directory is scanned at each LO start.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20180302
*** This bug has been marked as a duplicate of bug 39743 ***
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 https://cgit.freedesktop.org/libreoffice/core/commit/?id=c91f70f9b0129685737260c04a2e347726f1dedf 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.