https://bugzilla.redhat.com/show_bug.cgi?id=1530211
Akira TAGOH <tagoh(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #10 from Akira TAGOH <tagoh(a)redhat.com> ---
Thanks. I've tracked it down. matching rules which was added during <include>
was evaluated prior to rules added before <include>. so even though xterm is
requesting "mono" - which is usually corrected to "monospace" by the
rule in
fonts.conf - 2.12.91 is adding "sans-serif" because none of
"sans-serif",
"serif", "monospace" is in the pattern, then evaluating a rule to
replace
"mono" to "monospace" at the end. so 2.12.91 is returning a sans-serif
font
instead of monospace.
Anyway, will fix that shortly.
--
You are receiving this mail because:
You are on the CC list for the bug.