Re: [ft] Windows font driver Parser

[Ammar ul hassan]

I found this internal Freetype document

http://www.fifi.org/doc/libfreetype6/freetype2/

It looks helpful but still no clue of how to understand the code flow and
how can we write our own driver module. I started windows font driver as
told that its the simplest but unable to figure it out that how it works.
some questions regarding that are below

1) On base layer i.e. in src/base directory there are different high level,
low level api's, font specific features with individual driver module
API's. So when are these Driver module API's called like in case of windows
font driver when this ftwinfnt.c is invoked.

2) Are driver modules only called by ftobjs.c where it checks which driver
to choose and than the driver who successfully parses the font file is
selected?





On Thu, Aug 3, 2017 at 11:46 AM, Ammar ul hassan <
address@hidden> wrote:

> >From that it sounds more like you're trying to write your own new driver...
>
> Yes actually i want to start my own driver later but first i need to 
> understand the flow of code so kindly guide accordingly.
>
> > 1) How windows font driver recognizes a window font file so that it can
> > parse it.
>
> Still no comments on this.
>
>
>
> On Wed, Aug 2, 2017 at 11:21 PM, Ammar ul hassan <
> address@hidden> 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?
>>
>> 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
>> 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)
>>
>
>