Then there is no point in using FreeType for loading font files at all,
(or adding support for new font file formats to FreeType) since FreeType
can load fonts from memory.
Do you mean that in AddFontResource I shouldn't try to call
WineEngAddFontResourceEx but do only a LoadLibraryEx (that won't work as
at least according to MSDN the parameter to AddFontResource can be a FNT
file or a Win16 NE executable) or that in AddFileToList I should not
make a distinction between memory and file fonts but always load the
font from memory, mmaping it before if necessary?
This code snippet causes a stack corruption since load_enumed_resource
has
wrong calling convention. I wonder whether gcc issued a warning here.
Thanks for catching it. I haven't noticed a warning but I think there
should have been one.
Mikolaj Zalewski
