https://bugs.kde.org/show_bug.cgi?id=487714
--- Comment #16 from Daniel Pereira <[email protected]> --- Reviewing the change aforementioned, it doesn't seem to line up with the comment #10, and that indeed seems to be the cause of the issue above. Adding a comma or not should probably be delegated to Pango FontDescription#to_string, but I assume adding the dependency might be cumbersome. Using heuristics to generate it might work for now, but it's fragile to future changes or conditions we aren't aware of. If we decide to go down this route, in my tests, it seems that the comma is only added after the font name when it has spaces (ex.: "Roboto Condensed") -- You are receiving this mail because: You are watching all bug changes.
