Fontconfig - Nov 2006 - Re: Luxi Mono

>|> Is the lack of "spacing=100" for Bold [Oblique] significant?
If so, why
 >|> are Bold [Oblique] not properly tagged?
 >|
 >|The lack of the spacing values is significant; this value is determined
 >|by examining the font and checking the spacing of each glyph; fonts
 >|where glyphs have different spacing values will not be marked as
 >|monospace 
 >|
 >|Using fontconfig 2.4.1, you could override this by editing the spacing
 >|value detected in the font with the configuration file.

I tried the following:

 <match target="font">
   <test name="family">
      <string>Luxi Mono</string>
   </test>
   <edit name="spacing" mode="assign">
     <int>100</int>
   </edit>
 </match>

but it didn''t seem to have the desired effect.

On Fri, 2006-11-03 at 12:18 -0500, Bob Tennent wrote:
> I tried the following:
> 
>  <match target="font">
>    <test name="family">
>       <string>Luxi Mono</string>
>    </test>
>    <edit name="spacing" mode="assign">
>      <int>100</int>
>    </edit>
>  </match>
target="scan"

should do the trick; that affects the pattern constructed when scanning
the file. The "font" rules are not applied until an application is
about
to draw with the font, long after the font was selected.

-- 
keith.packard@intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :
http://lists.freedesktop.org/archives/fontconfig/attachments/20061103/636d2a70/attachment.pgp