Re: [ft-devel] Contribution to freetype

[Parth Wazurkar]

>Well, most of the time it will be rather `add new header files'.
> >Modifications to other header files will (hopefully!) be minor only.
>
 Yes!


> >I'm thinking of handling files like Microsoft's
> >`GlobalSerif.CompositeFont'.  Apple and Android provide similar
> >concepts.

>It's probably not the job of FreeType to digest such
> >composite fonts by itself (you'll need an external XML interpreter);
> >however, it would be very helpful if we have a foundation to
> >provide easy support for such composite fonts.
>
Can you please provide me some resources so that I can study this part and
allot a time slot for its implementation in the GSoC timeline.

Thank You

Regards
Parth
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: [ft-devel] Contribution to freetype

[Werner LEMBERG]

> For the project, I am thinking of the following approach: I will
> have to modify the internal freetype files which provide the support
> to the new font format drivers.

Well, most of the time it will be rather `add new header files'.
Modifications to other header files will (hopefully!) be minor only.

> Further, I will have to implement new drivers for gf, pk, tfm and vf
> font formats for freetype.

Yep.

> For the drivers I will take reference from the available drivers in
> VFlib and implement them for freetype on the lines of already
> available bdf font format driver.

Exactly.  The BDF, PCF, and Winfnt modules can serve as examples how
bitmap drivers work, and the Type1 module shows how to `attach' a
metric file to a font.

> I recognize that for the `vf` font format support it is tagged as
> 'hard' and I fear I may have missed things that might make it more
> difficult than I imagined.

The difficulty is not adding support for the VF format itself but to
find a good API that is generic enough for other purposes, too.  I'm
thinking of handling files like Microsoft's
`GlobalSerif.CompositeFont'.  Apple and Android provide similar
concepts.  It's probably not the job of FreeType to digest such
composite fonts by itself (you'll need an external XML interpreter);
however, it would be very helpful if we have a foundation to
provide easy support for such composite fonts.


Werner

___
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: [ft-devel] Contribution to freetype

[Parth Wazurkar]

Hi,
For the project, I am thinking of the following approach:
I will have to modify the internal freetype files which provide the support
to the new font format drivers. Further, I will have to implement new
drivers for gf, pk, tfm and vf font formats for freetype. For the drivers I
will take reference from the available drivers in VFlib and implement them
for freetype on the lines of already available bdf font format driver.
I have an idea on how to progress for the coding part. I want to ask if
this approach is correct? and do you suggest any modifications so that I
can come up with a detailed proposal asap which we can discuss further.
I recognize that for the `vf` font format support it is tagged as 'hard'
and I fear I may have missed things that might make it more difficult than
I imagined. I would really appreciate any guidance or comments.

Regards
Parth

On Fri, Mar 16, 2018 at 9:31 AM, Parth Wazurkar 
wrote:

> Thank you so much Ewald.
> I'll check that out.
>
> Regards
> Parth
>
>
> On Fri, Mar 16, 2018 at 9:13 AM, Ewald Hew  wrote:
>
>> Hi Parth,
>>
>> > I am unable to figure out the working of `FT_Face_InitFunc` in the
>> `ftdrv.h`
>> > file.
>> > particularly, how does the call to `init_face` function invokes the
>> > particular font format's driver.
>> > Please help.
>>
>> I suggest you read the article here
>> , which
>> goes into some detail about how interfaces are being implemented in
>> FreeType.
>>
>> Basically, `FT_Face_InitFunc' is a function pointer type (with its
>> signature), through which the driver-specific implementation of
>> `init_face' can be set, per module. Look up the `FT_DEFINE_DRIVER'
>> macro and where it's being used.
>>
>> Ewald
>>
>
>
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel