> I think this error means that the file was fond but the size 14 was not.
No, this is showing that size 14 VearBd.ttf is being requested. > The problem is that the TTF fonts are rendered and the files themselves do not contain sizes. There's a DPRINTF that can be changed to a printf in engine/devfont.c::GdCreateFont for the freetype driver. This will show whether the freetype driver accepted the font path string. > Are you using the latest patches. I thought this was fixed recently. I fixed NXLIB issues with ttf fonts, that had to do with matching XLFD strings in the fonts.dir file. The other fix, a couple of months prior, was implementing support for later versions for freetype, including 2.3.5. The issues there were related to not rotating properly, and having to have caching turned off for certain versions of FT2. Regards, Greg Greg Haerr wrote: > : fnt_fontcreate: VeraBd.ttf , 14 not found > > This means that the "nano-X format .FNT font" subdriver didn't find > the .ttf font, which it shouldn't. So this isn't an error. Your font > was likely selected and worked using the ft_ driver. > > I have a patch to change this printf behaviour, which I'll apply, to > make things less confusing. If you turn off FNT fonts in the config > file, this won't display. > Okay but it isn't rendering any text as well as getting that error. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
