[Fontconfig] monospaced fonts and combining characters: fontconfig bug?

Mike FABIAN mfabian at suse.de
Thu Jul 14 01:12:10 EST 2005

Fontconfig fails to detect that the "FreeMono" fonts are monospaced,
it doesn't set spacing=100:

mfabian at magellan:~$ fc-list FreeMono family style spacing 
FreeMono:style=BoldOblique,Negreta cursiva,tučné kurzíva,fed kursiv,Fett Kursiv,Έντονα Πλάγια,Negrita Cursiva,Lihavoitu Kursivoi,Gras Italique,Félkövér dőlt,Grassetto Corsivo,Vet Cursief,Halvfet Kursiv,Pogrubiona kursywa,Negrito Itálico,Полужирный Курсив,Tučná kurzíva,Fet Kursiv,Kalın İtalik,polkrepko ležeče,Lodi etzana
mfabian at magellan:~$

When checking why this happens, I found that the advance widths for
almost all glyphs in the "FreeMono" fonts are 600, *except* for U+0300
- U+0344 where the advance width is 0.

But all the characters in the range U+0300 - U+0344 are combining
characters and as I currently understand it, it is correct that the
advance width is 0 for combining characters.  It is like that in most
other fonts as well, for example in "Arial Unicode MS" (not
monospaced). "Courier New" is an exeption, it has the same advance
width for combining characters as for regular characters, therefore
fontconfig recognizes "Courier New" as monospaced.

Probably fontconfig should ignore all combining characters when
checking whether a font is monospaced.

Is that correct?

See also:


Mike FABIAN   <mfabian at suse.de>   http://www.suse.de/~mfabian

More information about the Fontconfig mailing list