Bug#1028897: fontconfig: wrong name for the Noto monospace font

[Gunnar Hjalmarsson]

Hi Raphaël!

Raphaël Halimi wrote:
> The problem is that the monospace Noto font is actually "Noto Mono" and
> not "Noto Sans Mono" (probably a typo on upstream's part).
> 
> If you use a font manager you'll see that there is indeed a font called
> "Noto Sans Mono", but if you filter them out to list only the monospace
> fonts, you can see that there's no font called "Noto Sans Mono" among
> them, but there is one called "Noto Mono".

That's a misconception, and upstream is to blame for it. Not 
Freedesktop, though, but Google.

Noto Sans Mono is a monospace font shipped by the fonts-noto-mono 
package in Debian. So is Noto Mono (previously named Droid Mono). The 
problem is that Noto Sans Mono does not declare itself as such properly. 
Please see this upstream gnome-terminal issue:

https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/7960

That should make you understand what it is I'm trying to say. :/

> Using this one (which I now believe is the "real" monospace font from
> Noto) as default for the monospace family does fix both Xterm and
> gnome-terminal (and probably other terminals too).

So you have found that the older Noto Mono font looks better in 
terminals than Noto Sans Mono. That's interesting.

In any case I'm pretty sure that there is no typo in 60-latin.conf, so 
your patch is based on false premises.

But with that said, if other users are of the same opinion as you, it 
may be motivated to consider a Debian patch as regards the default 
monospace font for latin scripts. Personally I can think that going back 
to DejaVu Sans Mono should should be a more natural step, in that case. 
Noto Mono isn't even mentioned in 60-latin.conf.

-- 
Cheers,
Gunnar Hjalmarsson