Created attachment 119803 [details] All styles of Sinkin Sans displayed in LibreOffice Steps to reproduce: 1. Install the font "Sinkin Sans" by K-Type. It is licensed under the Apache License and can be downloaded free of charge here: http://www.fontsquirrel.com/fonts/sinkin-sans 2. Open any component of LibreOffice that allows you to select a font. 3. Scroll down to the s's to find Sinkin Sans. Expected behaviour: In the font selection menu, LibreOffice displays the Sinkin Sans font as a single selectable font family. Actual behaviour: LibreOffice displays each individual style of Sinkin Sans as its own font family. Platform: Ubuntu 14.04 with xfwm4 4.11.1. This is because Sinkin Sans names each style with a number, rather than setting the "family name" PostScript property to a consistent string as is typical, and LibreOffice interprets them as different families. I have seen many other fonts that do this. Inkscape, however, can group Sinkin Sans into one family.
Created attachment 119804 [details] Inkscape correctly grouping Sinkin Sans into a single family
Confirmed. Win 7 Pro 64-bit, Version: 5.0.2.2 (x64) Build ID: 37b43f919e4de5eeaca9b9755ed688758a8251fe Locale: fi-FI (fi_FI)
Some other fonts with similar behaviour include Cooper Hewitt (http://www.fontsquirrel.com/fonts/cooper-hewitt) and Biryani (https://www.google.com/fonts/specimen/Biryani).
** 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 (5.1.6 or 5.2.3 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 helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20161108
Created attachment 140953 [details] Bug still present in 6.0.2.1 Bug is still present in 6.0.2.1.
** 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
*** Bug 140519 has been marked as a duplicate of this bug. ***
Created attachment 178797 [details] libreoffice 7.3.1.3 showing the issue with fira sans This is a *major* pain for users with large font families, see e.g. the example given by the user of the marked-duplicate bug 140519. I'm adding to this to point out that this bug is not, as far as I can tell, limited to unusual or broken font families. It applies to every font family I've ever tried that has more than four styles or weights. In fact, you can test it yourself with an open source font, Fira Sans: https://github.com/bBoxType/FiraSans I've attached a screenshot showing what my fonts menu in the LibreOffice UI looks like with this font installed. Other applications that I've tried, including Inkscape, KDE's Font Management tool, and fontmanager.github.io, all show 3 font families for Fira Sans: Fira Sans, FS Compressed, and FS Condensed. Underlying libraries also have support for this: pango-list shows the same three families. The especially annoying thing is that LibreOffice interpolates an italic, bold, and bold-italic font for most of these "families", so the Fira Sans Light "family" has a simulated bold option - instead of switching to Fira Sans Bold! This all *feels* like something that might at one point have been a conscious design decision, to work around the fact that styles aren't exposed very well in the LibreOffice UI (as far as I know, nowhere but the character format window), so perhaps this was originally thought to be a workaround to allow users to more easily choose variant font styles? I think the correct UI solution to this would be to make a style / weight drop down that's separate from the font family selector. Then the font name selector can be used exclusively to present different font families.
An ideal fix would allow configuring the font list from the GUI. Ubuntu-desktop installs international fonts by default, and the dropdown is cluttered by tons and tons of Indic and Asian fonts, even when the system language is set to English. It would be more or less trivial to put a list with checkboxes in the config menu.
(In reply to Coburn Ingram from comment #9) > An ideal fix would allow configuring the font list from the GUI. > > Ubuntu-desktop installs international fonts by default, and the dropdown is > cluttered by tons and tons of Indic and Asian fonts, even when the system > language is set to English. It would be more or less trivial to put a list > with checkboxes in the config menu. I think that's not a bad idea, though there's already a separate bug report for it: https://bugs.documentfoundation.org/show_bug.cgi?id=91130 In cases like the one this bug is about, the issue is that we *do* want to be able to access all the stylistic variants, but LibreOffice is treating them as if they were separate families.
We only support R/B/I/BI font family model for various legacy and compatibility reasons, and that is why families with styles other than these four get handles as separate font families. This is intentional and not a bug.