https://bugs.documentfoundation.org/show_bug.cgi?id=35538
--- Comment #91 from João Paulo <joaopauloag-freedesk...@yahoo.com.br> --- (In reply to Eyal Rozenberg from comment #90) > > Actually, using styles is generally a good idea, not an ugly workaround - > but if one already uses styles, one should avoid emulating all kinds of DF, > and rather use styles with semantic meaning. :-) Oh, I didn't express myself correctly, it's not the use of styles that is ugly (I love using styles), but the workaround I could come with that is ugly because it multiplies the needed styles to keep the document visual style consistent, i.e., (In reply to Eyal Rozenberg from comment #90) > > Same as my last screenshot; perhaps it has indeed gotten worse; or the font > has a newer version? I think it is because of the new version (I noticed this bug got worse when I updated the font file). Even if the regression is on the font itself (the older version used to show all the variants inside a single typeface family -- maybe a compatibility tag was removed?), there are lots of other fonts that also show up on LibreOffice as different typeface families instead of a single grouped family: * Arial Nova is shown as Arial Nova, Arial Nova Light, Arial Nova Cond, Arial Nova Cond Light); * Bahnschrift (a single variable font file) is almost a nightmare: it is shown as Bahnschrift, Bahnschrift Condensed, Bahnschrift Light, Bahnschrift Light Condensed, Bahnschrift Light SemiCondensed, Bahnschrift SemiBold, Bahnschrift SemiBold Condensed, Bahnschrift SemiBold SemiConden, Bahnschrift SemiCondensed, Bahnschrift SemiLight, Bahnschrift SemiLight Condensed, Bahnschrift SemiLight SemiConde. The truncated names are a limitation of LibreOffice, as Windows 11's Control Panel and the Settings app (and I think Windows 10 also) shows the names completely; * Calibri is shown as Calibri and Calibri Light; * Candara is shown as Candara and Candara Light; * Cascadia Code is shown as Cascadia Code, Cascadia Code Extra Light, Cascadia Code Light, Cascadia Code SemiBold, Cascadia Code SemiLight; * Cascadia Mono has the same variants as Cascadia Code; * Corbel is shown as Corbel and Corbel Light; * and many other examples. Those typeface families (all provided by Microsoft, in Windows 10 and 11) are grouped correctly by the Control Panel and the Settings app, i.e., they are shown as a grouped font icon with the typeface family name (Bahnschrift, for example) and when that icon is opened then it shows all the typeface members of the family. Even the Merriweather Sans typeface family shows up nicely grouped together in Control Panel and the Settings app, so it's safe to assume that LibreOffice doesn't use the better API to handle fonts and typeface names with more than the classic R/B/I/BI variants. > Actually, using styles is generally a good idea, not an ugly workaround - > but if one already uses styles, one should avoid emulating all kinds of DF, > and rather use styles with semantic meaning. :-) The ugliness doesn't come from using styles, but from having to use extra styles that has "another" typeface set instead of just another style (bold, italic, bold italic, light, regular, etc.) on that typeface family, which makes it easy to make a mistake when changing typefaces on the base style. Instead of a single character style named Emphasis that just adds the bold style to the typeface, I have to use a secondary "Emphasis Merriweather Light to Bold", a secondary "Emphasis Cascadia Light to Bold", and so on, to avoid using fake emboldened fonts. -- You are receiving this mail because: You are the assignee for the bug.
