Comment # 52 on bug 951898 from Felix Miata

(In reply to yzT yzT from comment #51)

> fc-match returns SourceCodePro-Medium.otf: "Source Code Pro" "Medium"

Did you write what you meant to write? Did you mean

    fc-match monospace

returns

    SourceCodePro-Medium.otf: "Source Code Pro" "Medium"

???

> Monospace font (in Gnome Tweak Tools) is defined as Monospace Regular. It

Monospace is most appropriately defined as the generic fixed pitch/fixed width
font akin to serif and to sans-serif, used in both fontconfig and CSS. There is
an actual font named Monospace that's part of a ghostscript package, which can
cause inexplicable behavior.

> looks like you replaced Monospace font with Source Code Pro, because if for

I didn't submit any patches to change Leap's font defaults. I'm an interested
observer.

> example I change the Terminal font (default to Monospace Regular) to Source
> Code Pro, it looks exactly the same.

This indicates the bug "fix" is working as intended, defining the fontconfig
global monospace font as Source Code Pro, with nothing on your system to
override it.

> However, in any other distro, Monospace Regular looks like it must be.

I cannot parse this.

> The IRC application is HexChat, but that's irrelevant, the same font is
> spread system-wide (e.g. Terminal or Gedit).

I just wanted to be sure the font wasn't defined within the IRC client rather
than inheriting the fontconfig monospace definition. It indicates the "fix" is
working as intended, defining the fontconfig global monospace font as Source
Code Pro, with nothing on your system to override it.