> I came across the description of `FT_Module_Class' in `ftmodapi.h',
> I found that there is no description of `module_interface' field in
> its description. I doubt this is intentional and maybe it is an
> oversight. Maybe its description can be added too.
Indeed. A description was missing
Hi all,
I came across the description of `FT_Module_Class' in
`ftmodapi.h', I found that there is no description of
`module_interface' field in its description. I doubt this is
intentional and maybe it is an oversight. Maybe its description
can be added too.
Thank you
Parth
>
> > I found out `T1_CONFIG_OPTION_NO_AFM' option, should we have such an
> > option like `TEX_CONFIG_OPTION_NO_TFM' for our tfm driver? What do
> > you suggest.
>
> I think this is not necessary. There are other possibilities to not
> compile the GF/PK/TFM/VF combo (namely, to omit the
> I found out `T1_CONFIG_OPTION_NO_AFM' option, should we have such an
> option like `TEX_CONFIG_OPTION_NO_TFM' for our tfm driver? What do
> you suggest.
I think this is not necessary. There are other possibilities to not
compile the GF/PK/TFM/VF combo (namely, to omit the corresponding
>
> >> A separate TFM module makes sense IMHO, since exactly the same code
>> >> will be used for the PK module also. And VF will need this, too.
>> >> Compare this to the `psaux' module which provides routines for CFF,
>> >> Type1, Type42, and CID fonts.
>> >
>> > Can you please tell me which
>
> >> A separate TFM module makes sense IMHO, since exactly the same code
> >> will be used for the PK module also. And VF will need this, too.
> >> Compare this to the `psaux' module which provides routines for CFF,
> >> Type1, Type42, and CID fonts.
> >
> > Can you please tell me which files
> Very nice, thanks! Note that all links currently fail (it misses a
> `reference' subdirectory in the link).
>
Oops, this is fixed now.
--
Nikhil
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
>> A separate TFM module makes sense IMHO, since exactly the same code
>> will be used for the PK module also. And VF will need this, too.
>> Compare this to the `psaux' module which provides routines for CFF,
>> Type1, Type42, and CID fonts.
>
> Can you please tell me which files should I look
>
> >> Please have a look how AFM files are attached to Type 1 fonts; it
> >> basically does the same, namely to add more metric information. I
> >> suggest that you use this as a template.
> >
> > If we use this as a template, then there is no need to have a
> > separate TFM driver, as VFlib's
>> Please have a look how AFM files are attached to Type 1 fonts; it
>> basically does the same, namely to add more metric information. I
>> suggest that you use this as a template.
>
> If we use this as a template, then there is no need to have a
> separate TFM driver, as VFlib's TFM driver
>
> > Ok, then I have a pretty clear idea about how to accomplish it, I
> > will create some API functions in the `tfm' driver's service code
> > which will be used in the `gf', `pk' and `vf' drivers to extract the
> > tfm data.
>
> Please have a look how AFM files are attached to Type 1 fonts; it
11 matches
Mail list logo
