> > The problem might be that the glyph drawing backend calls a
> > convenient function provided by freetype to embolden the glyphs,
> > which lacks parameters to control how embolden is done.
>
> Is it considered a bug?
No. Embolding with fixed values is always problematic. Recent
FreeType version have a function which enables the user to fine-tune
the boldness.
> > Another solution is to convert the font to a bitmap one for the
> > pixel size used. The convenient function uses different algorithm
> > to embolden bitmap glyphs, which is similar to what Windows does.
>
> It seems that ttf2bdf doesn't want to generate a bold version of a
> font even when "-w Bold" option is used,
Uh, oh, ttf2bdf uses FreeType 1 which isn't supported since years.
The -w option of ttf2bdf doesn't modify the font at all, it only
adjusts the used X Windows font name within the BDF file.
> though it is possible that I missed something while reading a map
> page, going to take a better look at it later. In any case, the best
> option is to make an original .ttf look good.
I suggest to use FontForge to do what you want. This can be
controlled with scripts also.
Werner
_______________________________________________
Freetype mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/freetype
