On Wed, Aug 2, 2017 at 7:21 AM, Ammar ul hassan <[email protected] > wrote:
> 1) How windows font driver recognizes a window font file so that it can > parse it. > > Like in Type 1 driver module case there is a file t1parse.c which actually > checks the header of a file that, if it starts with some specific text than > this driver is selected for further parsing and so on. > > 2) Is there any guide for the developer so that they can understand the > flow of Freetype how code flows from start to end? > > https://www.freetype.org/freetype2/docs/documentation.html ? > In my case i just want to read type1 font file or winfnt font file and > check the number of faces, font family name, style name etc. I can get the > https://www.freetype.org/freetype2/docs/reference/ft2-base_interface.html#FT_New_Memory_Face or https://www.freetype.org/freetype2/docs/reference/ft2-base_interface.html#FT_New_Face https://www.freetype.org/freetype2/docs/reference/ft2-base_interface.html#FT_Open_Face (has definition of of face_index) start with face_idx = 0 the resulting ft_face ( https://www.freetype.org/freetype2/docs/reference/ft2-base_interface.html#FT_FaceRec ) as its first entry is num_faces; num_glpyhs, also is family_name, style_name, etc. once you get num_faces you can get the styles/family names of the other faces by repeating FT_New_face for each face_index. > desired output but unable to find that when code executes how it goes to > base layer where ftobjs.c resides and how respective driver module calls > all functions for further operation. (starting point of driver module so > that i can do forward/back tracking if no doc available) > >From that it sounds more like you're trying to write your own new driver... > _______________________________________________ > Freetype mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/freetype > _______________________________________________ Freetype mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype
