I am using Libreoffice 4.0.3.3 on Windows XP x64. In Libreoffice, Liberation Sans/SansNarrow/Serif/Mono fonts do not display correctly when neither bold or italic is used. They get displayed as a generic monospace font (Courier New). Bold or italic versions are fine. In the Windows font preview, the Bold/Italic/BoldItalic version display fine, but the Regular version displays a blank page (metadata is not displayed, and even the "(Truetype)" suffix is missing). This is certainly related to Bug 62764.
Created attachment 80634 [details] font preview for Liberation Sans Regular
Created attachment 80635 [details] font preview for Liberation Sans Bold
I can confirm this bug on my Windows 8 machine after updating from Libreoffice 3.6 (normal font display of Liberation sans) to 4.0. Now everything looks monospace and breaks my documents, but Liberation Sans is still displayed as selected font, so it is a displaying problem. Since this is a show stopper and breaks fundamental user experience, I triage this as major.
@kookoo: Your first screenshot doesn't show much of a font preview (almost everything on this image is white), so maybe this is part of the problem.
After some more testing, it seems this is _not_ a Libreoffice bug but a bug between the Liberation font and Windows. It's because the wrong displaying also occurs, when one changes the font in the Windows Editor to one of the Liberation fonts, so it's not Libreoffice specific, but appears one updates/installs Libreoffice. Fix: Install the newest version of the Liberation font 2.00 from https://fedorahosted.org/liberation-fonts/. Windows needs a restart, if you only copy the ttf's to %windir&\fonts instead of installing them. This is bug report should still be kept open, since Libreoffice should not distribute a font version with bugs, so this should be fixed in the next minor release.
5 months after reporting this reproducible bug and 2 months after a fix was suggested (distributing the Windows version of LO with a newer Libreation font version) no responsible maintainer seems to care.
(In reply to comment #6) > 5 months after reporting this reproducible bug and 2 months after a fix was > suggested (distributing the Windows version of LO with a newer Libreation > font version) no responsible maintainer seems to care. Hi, The problem is that 4.0\4.1 *does* come with version 2.0 of liberation fonts. Just checked with 4.0 & 4.1.3 installers, and the included fonts are bit-to-bit identical to the ones from the official Liberation fonts site.
(In reply to comment #7) > The problem is that 4.0\4.1 *does* come with version 2.0 of liberation > fonts. Just checked with 4.0 & 4.1.3 installers, and the included fonts are > bit-to-bit identical to the ones from the official Liberation fonts site. As a fact, an upgrade from 3.6 to 4.0 breaks it (but apparently not for all users) and installing the font manually repairs it. What didn't repair it, was downgrading and reupgrading, so something with the installer seems to be wrong. I don't know that stuff, but on Windows you need to kind of register a new font? Did 3.6 use another versions of the font?
(In reply to comment #8) >Did 3.6 use another versions of the font? Indeed, 3.6 came with version 2.00.0 of the fonts, while 4.0 & 4.1 come with 2.00.1.
I can't reproduce that bug with a clean installation of Windows 7 (32-bit). First I installed 3.6.7, then upgraded to 4.0.3. The installer successfully replaced old fonts with the new ones. The fonts are working perfectly after that. Anyway, would be great if you could test it with the latest version of LibreOffice (4.1.3).
(In reply to comment #10) > I can't reproduce that bug with a clean installation of Windows 7 (32-bit). The initial bug reporter used Windows XP and I had this bug only on Windows 8 (two Windows 7 machines hadn't this issue, I upgraded them on the same day). Can you try to reproduce it with XP or 8?
(In reply to comment #11) >Can you try to reproduce it with XP or 8? Can't reproduce also with XP SP3 (32-bit). Don't have XP 64-bit or Windows 8.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: *Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.1 or later) https://www.libreoffice.org/download/ *If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior *If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT *Update the version field *Reply via email (please reply directly on the bug tracker) *Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18
Never had this problem on Win. Issue seems obsolete now (3.6 - 4.0). Setting to WFM. If the reporter still suffers from this, they can set back to NEW.
This issue seems to be back for me now, in LibreOffice 6.1.0.3 (x64). About LibreOffice screens shows this: Version: 6.1.0.3 (x64) Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1 CPU threads: 8; OS: Windows 6.1; UI render: default; Locale: en-US (en_US); Calc: group threaded This was working prior to my LibreOffice install updating itself to the latest version on September 4th. Liberation Sans, Liberation Sans Narrow and Liberation Serif all look like Liberation Mono.
(In reply to Kerry Hjertaas from comment #15) > This issue seems to be back for me now, in LibreOffice 6.1.0.3 (x64). > > About LibreOffice screens shows this: > > Version: 6.1.0.3 (x64) > Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1 > CPU threads: 8; OS: Windows 6.1; UI render: default; > Locale: en-US (en_US); Calc: group threaded > > > This was working prior to my LibreOffice install updating itself to the > latest version on September 4th. Liberation Sans, Liberation Sans Narrow > and Liberation Serif all look like Liberation Mono. New issue please. And, what is needed is a verbose installation log. i.e. from a Command prompt "Run as Administrator" command line: msiexec.exe /i LibreOffice_6.1.0.3_Win_x64.msi /L*v lo610installLog.txt Then, if issue actually is repeated, zip the logfile and attach to a new BZ issue.
(In reply to V Stuart Foote from comment #16) > (In reply to Kerry Hjertaas from comment #15) > > This issue seems to be back for me now, in LibreOffice 6.1.0.3 (x64). > > > > About LibreOffice screens shows this: > > > > Version: 6.1.0.3 (x64) > > Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1 > > CPU threads: 8; OS: Windows 6.1; UI render: default; > > Locale: en-US (en_US); Calc: group threaded > > > > > > This was working prior to my LibreOffice install updating itself to the > > latest version on September 4th. Liberation Sans, Liberation Sans Narrow > > and Liberation Serif all look like Liberation Mono. > > New issue please. And, what is needed is a verbose installation log. > > i.e. from a Command prompt "Run as Administrator" command line: > > msiexec.exe /i LibreOffice_6.1.0.3_Win_x64.msi /L*v lo610installLog.txt > > Then, if issue actually is repeated, zip the logfile and attach to a new BZ > issue. Kerry was not in CC, so adding to be sure. Kerry: you need to open a new report.