Re: [Freetype] Saving Memory using the ROM - API suggestion

[Dave Williss]

Should be fairly easy.  There's a replacement module for file IO that
replaces it with memory-mapped IO (using mmap).  Start with that and
modify it to just point to where the font is in ROM.  (I'm assuming you
have the actual ttf file burned in the ROM).

In fact here's a suggestion for the team:

Would it be possible to add an FT_Open_Face_In_Memory function
that instead of trying to open the font took a pointer to something already
read into memory?

This way reading a font in ROM would just be a simple function call and
you wouldn't have to hack the library source to do it.  It would have
greatly
simplified Mac OSX dfont rendering too, because it leaves the platform-
specific find-the-font-embedded-in-this-file bit up to the caller.
It would be up to the caller to free (if necessary) any memory after they
close the face.  Or perhaps have a way to register a free function that will
get called on close.

----- Original Message -----
From: "Nir Rostoker" <address@hidden>
To: <address@hidden>
Sent: Wednesday, December 05, 2001 5:48 AM
Subject: [Freetype] Saving Memory using the ROM


> Hi !
> Did any one tried the option of loading a Engine object and a Face object
to
> the ROM, and using the LoadGlyph()
> and RenderGlyph and SetSize() function on those objects in the ROM instead
> of having them on the RAM.
>
> I have started checking this idea, can anyone tell me if its possible ?
> should there be special problems with it ?
>
> Thanks,
> Nor
>
> _______________________________________________
> Freetype mailing list
> address@hidden
> http://www.freetype.org/mailman/listinfo/freetype