Quoting Jan Willem Stumpel ([EMAIL PROTECTED]): > It can. Just take the .sfd files for all FreeMono variants and > change all occurrences of Width: 0 to Width: 600 (version cvs-5 > did this only for characters whose width is not equal to 600 and > *not* equal to 0). It seems that really *all* characters must have > the same width, in order for a font to be recognised as > monospaced. Let fontforge generate new ttf files. The isFixedPitch > entry in the "post" table will now be *automatically* set to 1, so > ftinfo will give the correct result.
Great. This is somehting I was thinking about and already tried. Unfortunately, I missed that some *other* characters were *not* 600 wide...so my attempt failed. > I found that the characters which have Width: 0 in the present > version (the combining accents) do not suffer from having their > width changed from 0 to 600. They still work as combining accents Wonderful. So, now we're really close to the solution, indeed. Again, thanks a lot for pushing me on that way, Jan (or Jan Willem, as you prefer!).
signature.asc
Description: Digital signature
