TTFAutohint VF beta

[Dave Crossland]

https://gitlab.com/ewaldhew/tah-vf

Still a bit buggy but it's coming together

[Micah Stupak-Hahn]

Cool, thanks for the update. I'll throw some Open Sans at it and see what happens.

On Wed, Jul 11, 2018 at 11:31 AM Dave Crossland <dcros...@google.com> wrote:

https://gitlab.com/ewaldhew/tah-vf

Still a bit buggy but it's coming together

--

Micah Stupak-Hahn
Typographic Engineer
Measure + Fit
mi...@measureandfit.com

[Micah Stupak-Hahn]

Are you sure this is the version with VF capability? It's listed as 1.8.1 which is the same version released at the beginning of the year and available for download on freetype.org.

It also doesn't build properly on OS X anyway, so...

[Dave Crossland]

Try the https://gitlab.com/ewaldhew/tah-vf/tree/gvar-wip branch

[Dave Crossland]

Thanks for the explanation!! :) 

On Wed, Jul 11, 2018 at 12:33 PM Ewald Hew <ewal...@gmail.com> wrote:

Hi all,

Just to be certain, you should look at the `gvar-wip' branch, yes.
Also, it does not really have VF capability yet, as all I have
implemented so far is the parsing and conversion of the `gvar' table
to the `cvar' table, providing variation support for all the CVT
values needed by ttfautohint to do the rest of its job. In other
words, the output is a variable font but it does not have the proper
hinting for variation instances. Consider this a pre-alpha version, if
you will.

I will soon begin implementing the actual processing and generation of
glyph bytecode to support variations, having already designed a
solution. I will then work on reducing the output by improving the
glyph analysis step in ttfautohint.

Ewald

[Marc Foley]

Hey Ewald,

Do you have a working binary for OS X?

I followed the build instructions and I get the following traceback

--

Marc Foley

[Felipe Sanches]

Marc,

FT_Done_MM_Var is a variable-fonts related function that was added recently (last January).

Do you have a reasonably recent version of freetype installed on your system?

Release notes for Freetype 2.9 state the following:

"A new function `FT_Done_MM_Var' is provided to free the memory returned in a call to `FT_Get_MM_Var'."

https://sourceforge.net/projects/freetype/files/freetype2/2.9/

--
You received this message because you are subscribed to the Google Groups "Google Fonts Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to googlefonts-discuss+unsub...@googlegroups.com.
To post to this group, send email to googlefonts-discuss@googlegroups.com.
Visit this group at https://groups.google.com/group/googlefonts-discuss.
To view this discussion on the web visit https://groups.google.com/d/msgid/googlefonts-discuss/CADE4-W8nps3_h-Qz-OGB-Sq8pSvJvYY%2BTGAkZGzwMj3wka43jA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Marc Foley]

If anyone is interested, I've now built a standalone Unix executable for this version of ttfautohint, which I've attached.

I'm still testing it but so far the results are pretty decent.

[Stephen Nixon]

@marc, is this built from the branch at https://gitlab.com/ewaldhew/tah-vf/tree/vf2, or something else?

I'm hoping to make sure I have the latest version of TTFautohint-VF.

[Dave Crossland]

Marc is now on winter holidays  but  yes I think thats it

[Johannes Neumeier]

I see some documentation referring back to this ttfautohint-vf but is this still the latest version to be used for autohinting TTF VFs? What exactly does it to differently compared to the regular ttfautohint?

From the repo it is hard to tell if the 'vf' work stagnated in that branch 2 years ago or if it ever got merged into the master (if that was the intention)?