Whither fnt2bdf?

Huw Davies h.davies1 at physics.ox.ac.uk
Thu Jan 23 12:59:57 CST 2003

On Thu, Jan 23, 2003 at 10:21:12AM -0800, Alexandre Julliard wrote:
> Dan Kegel <dank at kegel.com> writes:
> > Does that mean Wine can natively handle .fnt fonts (which
> > X libraries can't natively, I believe) as client side X fonts?
> My understanding is that FreeType can support bitmap fonts, but that
> it's not implemented in Wine yet; Huw can give you the details. Anyway
> most of the need for fnt2bdf was to convert the Windows standard
> fonts, and these are basically all TrueType now.

Wine doesn't handle fnts quite yet.  However I've just added the
necessary functions to FreeType to enable Wine to get hold of all the
information it needs and hopefully I'll get time to finish the Wine
side of things soon.

The fonts we're missing out on are System, FixedSys, Terminal,
Courier, Small Fonts, MS Sans Serif and MS Serif (note there's also a
Microsoft Sans Serif, but that's TrueType and should work already).

There are also 3 'stroke' fonts called Modern, Roman and Script;
FreeType doesn't support this format yet, but they're as ugly as hell
so probably won't be missed.

> > I suppose Wine would need some user-space app to manage
> > these fonts, then?
> I guess we could have a font control panel at some point, but there
> isn't that much to manage anyway. As long as the font files are
> somewhere on the font path everything should just work.

Right.  We'll need to add support for using libfontconfig soon -
that'll mean we don't have to set up a font path manually.


More information about the wine-devel mailing list