UFO export

[raphaelbastide]

Exporting source files as UFO will allow a cross-software compatibility.
Example here.

[nclm]

Hello.

I’m wondering what would be the workflow for working with UFO? I was thinking about it for another project, and now I’m seeing this thread here.

• Alice makes modifications with Fontforge. She saves in sfd (or sfdir, see Move source files from sfd to sfdir #21), exports an ufo copy, exports the font file, generates the webfonts. Commit and pull request.
• Bob opens the ufo and makes modifications with Robofont. He saves the ufo, exports the font files, generates the webfonts. Commit and pull request. Note: The sfd is out of date!
• Camille, who uses Fontforge, wants to join. Either they opens the ufo and there should not be any problem (a new, updated sfd is saved), or they opens the outdated sfd and Bob’s edits are lost!

Having two source files seems tricky, but maybe there’s a way? Moving from sfd to all-UFO could be the way to go, but I believe there’s no way to use Fontforge as a native opening-editing-saving UFO application? Or sfd could just be temporary local work files for Fontforge users but not uploaded on Git.

[raphaelbastide]

Yes, all-UFO is the most appropriate process imo.

[raphaelbastide]

Also, we should consider to keep the last version only on the repo, and solve #7

[ms-studio]

Ok! Then let's move the src to UFO, and we can remove the sfd files by adding that extension to the .gitignore.

[davelab6]

👍

[nclm]

I started making the changes on my local copy, but I’m getting weird glyphs alterations when converting to UFO from Fontforge:

I will try with different options. We have to be extra careful and double check if nothing breaks in this conversion! We are also loosing the horizontal guides apparently, even with the ‘Save guides’ option on.

[nclm]

Can’t seem to make it work. What is happening is not some control points being scattered but actual points being added:

I wonder if it’s a Fontforge bug or a Karmilla issue (or both). We always get these warnings about our coordinates not being integers: maybe some decimal points values are interpreted as multiples points once converted to UFO?

[nclm]

For reference, here’s the SFD’s .glyph and the UFO’s .glif for that lowercase ‘e’:

• https://gist.github.com/nclm/e85bcb2c4f9c4c638782

Trying to read them to get what is happening…

[davelab6]

cc @frank-trampe