No subject

Mon May 10 16:13:56 PDT 2010

of 0 in luximr.ttf that fontconfig doesn't expect in this font which is
confusing it, and making it classify it as not monospaced.

Is this a bug in fontconfig's monospace recognition or a bug in the font?

Unfortuantely, due to the license on this font, we can't change the
glyphs in the font, but if that's where the problem lies, we could modify
the X.Org tarball to also install a fontconfig workaround such as:

<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
  <match target="scan">
        <test name="family">
                <string>Luxi Mono</string>
        <edit name="spacing"><int>100</int></edit>

It seems we're not the first to have hit this, but it doesn't look like
anyone got farther than suggesting a single-user workaround instead of
a fix to either the font package or fontconfig:

	-Alan Coopersmith-        alan.coopersmith at
	 Oracle Solaris Platform Engineering: X Window System

More information about the Fontconfig mailing list