Version 6.31 [October, 2018 release]
The following are the changes since the 6.30 [August, 2018 release] release of VTT:
Introduction of “follow gasp” mode where text displayed in VTT can follow gasp table settings. Previously, VTT supported editing of the gasp table but text displayed in VTT would not follow gasp table settings. The “follow gasp” mode is an optional mode where text displayed in the main windows, sample text view, waterfall view and char set view will render according to appropriate gasp table settings. For more details on this mode, see the updated help file, Using Visual TrueType: The Basics > Grid-fitting and Scan-conversion Procedure (gasp)
Various bug fixes. Bug fixes including fix bug with importing glyphs from a “large” font, fix tag swap bug in TSIC table which is source table for cvar variation table, fix autohinter bug.
Comments
Could you add ResYLink tool in future builds and shortcut for it like F1(YLink)+alt or something like that.
ResYDist is very useful but it’s time consuming to change YDist manually in VTT talk.
Shortcut for "Show fewer points" display option.
In some fonts, if I don't use Autohinter outline modification, VTT doesn't show necessary points because they are off-curve, or when I need to move points by hand, I must go to Display options (Ctrl+D) and click on "fewer points" opt, then, after making all corrections, repeat it. So it would be cool to increase speed up this with shortkey.
smthng like
instead of
https://github.com/jansindl3r/VTT-XML-update
I have done this tool to update VTT's exported XML file with all instructions to new glyph order of the same typeface you are working on in VTT. I did it for my own purpose and I thought that others might find it useful as well. If there is another way of doing this, sorry I didn't know about it. I tried to use Fonttools only and import SPI tables from one file to another but it failed when compiling in VTT. In some cases when compiled, contours behaved very weirdly.
I would appreciate any comment or recommendation for improvement.
Download it, run it in cmd with Python 3 and use --help to get hints on how to use it.
I hope that someone will find it useful
For composite glyphs it looks like this:
where 1209 and 118 on the 2nd and 3rd line are baseGlyphs id
so if you change glyph order those number must also change in exported VTT code.
It should work like this:
https://github.com/ViktorRubenko/font_scripts/blob/master/vtt_xml_update.py
Thanks for pointing out this, I didn't realize it. Don't you want to become a collaborator for this on GitHub? Or can I get inspired by your code? Does anyone actually use this to write their glyph programs? Punkier way would be to remove all glyph programs and let generate them in VTT from VTT talk. I have commited this solution for now. Works fine now
I use it for manual control positions of components.
For example:
this is what generated by autohint:
This is what you get by compiling VTT xml with empty Glyph program:
You can control both vertical and horizontal positioning by CALL[], 86 and CALL[], 87 assembler like commands
Because accents are slightly blurred with DirectWrite and changing round methods doesn't help.
It works in VTT preview, but not in browser.
I have Photoshop CC 19 with variable fonts support, but I can’t see a hinting through it.