Identifying the script version

Got a request? Post it here. Please do not post bug reports here.
Mike Thompson
Posts: 409
Joined: Sat Apr 03, 2004 11:10 pm
Location: Massachusetts

Identifying the script version

Postby Mike Thompson » Mon Apr 04, 2016 10:31 pm

All my fonts use the same script (well with some exceptions) so having just finished a round of updates I ask do they have the right version of the script? This is quite laborious to determine.

My own crude method is to put in deliberate mistakes that can be seen when the font is used by a word processor.

I thought of having an empty GPOS lookup such as 'pos-20140329-b' .
Better would be some metadata in the script itself.

A comment field would help.

Such identification should ideally be visible from the outside without opening the Designer Window or even without running Font Creator.

Mike Thompson
Hebrew Font Design

Bhikkhu Pesala
Top Typographer
Top Typographer
Posts: 6808
Joined: Tue Oct 29, 2002 5:28 am
Location: Seven Kings, London UK

Re: Identifying the script version

Postby Bhikkhu Pesala » Thu Dec 01, 2016 10:50 pm

I found that I could add a comment in Notepad:

# Comment added in Notepad and edited in the Code Editor.

It imports OK, and does not interfere with validation. However, if you export the script, the comments are stripped. So copy/paste to Notepad and save it from there if you need to modify a script while using the Code Editor.

I associated *.otlfd files with Notepad2 for easier editing.

I use the Windows filename to identify different script versions. I save all of my scripts in the same folder as my font projects and archive the entire folder with 7-Zip for backup purposes. After importing Garava Regular.otlfd into Garava Italic, running the Autokern wizard, and fixing any issues, I export it as Garava Italic.otlfd.
My FontsReviews: MainTypeFont CreatorHelpFC11.0 Pro + MT7.0 @ Win10 1703

Return to “FontCreator - Requests and Enhancements”

Who is online

Users browsing this forum: No registered users and 1 guest