In my experience, FT_New_Face will not load the entire font into memory. However, for me this caused a lot of problems, and my preferred route was to load the font file myself and then call FT_New_Memory_Face.
It sounds like you might want the opposite -- for as much of the font file to stay out of memory as possible -- but you are not really in control of that either. The best you could do is kind of hope. If you are worried about the size of a font file, then perhaps you may want to go a more economical route, like just using a bitmapped font with homebrew rendering code, rather than a ttf. But I do not think I would attempt to run FreeType at all on a system with 256kb of RAM. Are you sure you don't mean 256MB? leesky wrote: > dear supports, I am a freshman using freetype. I have read "FreeType 2 > Tutorial Step 1 ― simple glyph loading ". > There are some important APIs explained. Create a new face object by > calling > FT_NEW_FACE(library, "/usr/share/fonts/truetype/arial.ttf", 0, &face ). > I am not sure whether the font file, "arial.ttf", will be loaded in > the memory entirely. > It's important for my embeded system, since my embeded system just has > 256kb memory, there must be more than 130kb for applications and RTOS. > Thank for your answer! > yours sincerely > Su > > ------------------------------------------------------------------------ > 使用新一代 Windows Live Messenger 轻松交流和共享！ 立即体验！ > <http://messenger.live.cn/> > ------------------------------------------------------------------------ > > _______________________________________________ > Freetype mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/freetype > _______________________________________________ Freetype mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/freetype
