>> Currently the research aim is to create a driver module for METAFONT.
>
> Somehow I don’t think that’s going to work...
Not necessarily, if you take METAFONT as an umbrella name for
everything related to it, for example METAPOST. Today's computer are
quite fast so that even complex operation
On Thu, 3 Aug 2017 14:48:01 +0900, Ammar ul hassan wrote:
> Currently the research aim is to create a driver module for METAFONT.
Somehow I don’t think that’s going to work...
___
Freetype mailing list
Freetype@nongnu.org
https://lists.nongnu.org/mailm
Currently the research aim is to create a driver module for METAFONT. After
this driver module the main target is to create a new font language that
will overcome the deficiencies of METAFONT i.e METAFONT converted to a new
programmable font language that will be much faster than it, covering all
i
> What you *really* want is to find out how FreeType is doing that so
> that you can write your own stuff, right?
>
> Yes i want to write my own stuff for Freetype, adding a new driver
> module more specifically.
Please give more details. What font format are you going to support?
Werner
_
> What you *really* want is to find out how FreeType is doing that so
that you can write your own stuff, right?
Yes i want to write my own stuff for Freetype, adding a new driver module
more specifically. So for that i need to understand how the code really
works.
> from experience I know
that w
> I found this internal Freetype document
>
> http://www.fifi.org/doc/libfreetype6/freetype2/
Ah, a very old version of
https://www.freetype.org/freetype2/docs/design/index.html
(I provided the link already in a previous e-mail).
It seems that the old document contains slightly more informa
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 ho
>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 n
[talking about the current git version of FreeType]
> 1) How windows font driver recognizes a window font file so that it can
>parse it.
I suggest that you use a debugger.
. Set a breakpoint at line 2255 in file `ftobjs.c' (in function
`ft_open_face_internal'). Here the central loop
On Wed, Aug 2, 2017 at 7:21 AM, Ammar ul hassan 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 tha
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 th
11 matches
Mail list logo
