>> Also, I just ran into the issue of `FT_Stream_OpenGzip' requiring the >> stream to having a valid `memory' field, which is not provided by >> `FT_Stream_OpenMemory' (for obvious reasons). > > This looks like a bug, both in documentation (which doesn't mention > it) and implementation (which doesn't correctly check for a valid `memory' > field). > >> Anyways ... would it be a good idea to add that requirement (a valid >> `memory field') as defined precondition of `source' to >> `FT_Stream_OpenGzip' etc.? > > Yes. Please provide a patch :-)
Sure, please find it attached :) -- were you thinking of something like that? If so, I can gladly push it with a ChangeLog entry, otherwise I'd kindly ask for change requests ;)
stream.patch
Description: Binary data
_______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
