https://bugs.documentfoundation.org/show_bug.cgi?id=35538
--- Comment #89 from João Paulo <[email protected]> --- Created attachment 194118 --> https://bugs.documentfoundation.org/attachment.cgi?id=194118&action=edit Merriweather Sans showing as three different typeface's families. I think the problem got worse, as now the Merriweather Sans typeface family (the latest version available at "https://github.com/SorkinType/Merriweather-Sans";) shows as three different typeface's families. It is bad because when we chose the Merriweather Sans Light ("Claro", in PT-BR), if we apply the bold style (either with the toolbar button or with the "Emphasis" character style), LibreOffice Writer applies a fake bold style derived from the Merriweather Sans Light instead of getting the Merriweather Sans Bold. A (ugly) workaround is creating several styles to choose, but it easily gets prone to errors: * My documents are formatted with both the Merriweather Sans Regular (for the main body text) and Light styles (for the quotation blocks), and I have to use two character styles for emphasis (the default "Strong Emphasis" character style that adds only bold and a dark-green color to the characters, and an additional, custom, "Emphasis on light to bold" that selects the Merriweather Sans Bold and a dark-green color to the characters -- this is needed to avoid the fake Merriweather Sans Light-Bold typeface; * If I decide to use another typeface, say Times New Roman, and change the Default Paragraph Style to use it (as it will reflect on "Body Text" and "Block Quotation" paragraph styles), the "Strong Emphasis" is correct as it only adds bold to the character that has it applied, but the custom "Emphasis on light to bold" character style will change the typeface from Times New Roman to Merriweather Sans Bold; * If the document has other custom character styles, such as styles that apply UPPERCASE, Small Capitals, other colors etc., there will be a need to change every character style to reflect the new default typeface selected on the document, and it gets very easily error-prone besides tedious. -- You are receiving this mail because: You are the assignee for the bug.
