Dmitry Timoshkov pisze:
"Mikolaj Zalewski" <[EMAIL PROTECTED]> wrote:
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?
I mean that we should choose from either leaving the task to FreeType,
or doing the whole job of loading the font files internally in Wine.
I admit I don't understand - what would we gain from doing all the
loading internally in Wine? Wouldn't that be simply rewriting a big part
of freetype? You wrote that loading fonts from memory will help but
isn't FT_New_Memory_Face using the same parsing code as FT_New_Face and
only the source differs? Anyhow it looks to me as something rather
orthogonal to this patch as I don't try to parse the content of the font
but only remove the PE "wrapping".
Mikolaj Zalewski
