Code formatting messed up...

[Jonathan Busby]

(11-10-2018 10:31 PM)ijabbott Wrote:  I don't know if Firefox's rendering engine (Gecko) uses the standard Linux desktop font glyph substitution mechanisms, but it probably uses the standard Linux fontconfig to perform font name substitution at least. So out of interest, what does the fc-match command show for "Monaco", "Consolas", "Courier", and "monospace" on your system? On mine, I get:

Code:

$ fc-match Monaco
DejaVuSans.ttf: "DejaVu Sans" "Book"
$ fc-match Courier
LiberationMono-Regular.ttf: "Liberation Mono" "Regular"
$ fc-match Consolas
DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"
$ fc-match monospace
DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"

It didn't really find a match for "Monaco" at all and just spat out a default in that case, but for the others it at least recognised them as monospaced fonts and did its best to find an appropriate match.

From the small screenshot you posted, it looks like it might have matched Courier to "Nimbus Mono L Regular", which at least for the Type 1 font from Debian's "gsfonts" package, only contains a couple of Greek characters: Δ and μ. So any other Greek characters will be pulled in from other fonts installed on the system.

I think you're right. Here's the output of fc-match on my Linux box :

Code:

$ fc-match Monaco
DejaVuSans.ttf: "DejaVu Sans" "Book"
$ fc-match Courier
n022003l.pfb: "Nimbus Mono L" "Regular"
$ fc-match Consolas
DejaVuSans.ttf: "DejaVu Sans" "Book"
$ fc-match monospace
DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"

Jonathan