<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Liberation fonts downgraded to 2.00.3 after LibreOffice 7.2 is installed"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=144443#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Liberation fonts downgraded to 2.00.3 after LibreOffice 7.2 is installed"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=144443">bug 144443</a>
from <span class="vcard"><a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> <span class="fn">Mike Kaganski</span></a>
</span></b>
<pre>Created <span class=""><a href="https://bugs.documentfoundation.org/attachment.cgi?id=174977" name="attach_174977" title="Liberation fonts showing file versions in MSI for 7.2.0">attachment 174977</a> <a href="https://bugs.documentfoundation.org/attachment.cgi?id=174977&action=edit" title="Liberation fonts showing file versions in MSI for 7.2.0">[details]</a></span>
Liberation fonts showing file versions in MSI for 7.2.0
(In reply to Roman Kuznetsov from <a href="show_bug.cgi?id=144443#c2">comment #2</a>)
<span class="quote">> Mike, should we update the fonts in LibreOffice distribution</span >
No idea; I don't track updates of fonts.
<span class="quote">> or may be the installer should check already installed fonts and if there
> are the fonts in OS LibreOffice shouldn't downgrade it to previous version?</span >
Sure. And we already made sure to include font versions to the installer
metadata (<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - disappear Noto fonts after install LibreOffice 6.0.3.1 on Windows 10"
href="show_bug.cgi?id=116581">bug 116581</a>). And they are indeed in the package.
I didn't try to repro myself; but I suspect that MS does something strange when
installing fonts for all, which doesn't allow to detect version downgrade.
At any case, a full install log is required, as with any installer issue; the
procedure is described at [1].
I don't really think we may (or should) do anything if that's some MS bug.
[1]
<a href="https://wiki.documentfoundation.org/Faq/General/General_Installation_Issues_(Windows#Create_an_installation_log">https://wiki.documentfoundation.org/Faq/General/General_Installation_Issues_(Windows#Create_an_installation_log</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>