Support OperatorMono-Book about operator-mono-lig HOT 20 CLOSED

I have started the ligatures for Operator Mono Book, as well as the ScreenSmart (SSm) versions. I hope to have these out by early next week.

from operator-mono-lig.

I switched to an app called Glyphs on the Mac. It seems to be much easier to use than FontForge. Here's a screenshot of me working on the ligatures.

from operator-mono-lig.

We're getting close!

from operator-mono-lig.

Sorry for the delay in getting the updated font weights. Work has been pretty hectic the past few weeks.

Also, one of the challenges is that when FontForge/Glyphs generate the actual outlines, they try to optimize by grouping similar instructions into subroutines. Normally this would be fine, but since I'm patching the existing font files with the new ligature outlines, the subroutine indices from the ligatures don't match (or don't exist) in the original font.

I was able to get away with it somewhat in the original version by tweaking the outlines a bit until I had no common entries. Needless to say this was pretty time consuming. Also Glyphs seems to be much more aggressive in finding common segments, so it was getting next to impossible to eliminate all callsubr/callgsubr entries, especially with hinting.

Therefore, I had to update the patching routine to re-write and re-index the subroutines as well. This also includes subroutines that call other subroutines. Yuck!

Anyway, hope to finish up these fonts over the next couple of days. Thanks for your patience.

from operator-mono-lig.

@kiliman I made manual/hacky changes to use the 'Book' font weight. It worked beautifully for me.
https://github.com/kennyklee/operator-mono-book-lig

All, this forked project worked great for me. All credit belongs to @kiliman.

from operator-mono-lig.

Thanks for checking out the project. I hope the instructions were clear.

Creating the actual ligatures wasn't too difficult, once I figured out how to use FontForge. The hardest part was figuring out how to extract and merge the ligatures themselves, since I can't distribute the actual font files.

Now that I've got that process down, I can work on creating ligatures for the other weights.

from operator-mono-lig.

Yes, the instructions are very clear. I have successfully created OperatorMono-Medium.😀

from operator-mono-lig.

Same here. The medium size is too thick for me. I might look into this eventually if you don't, but for now might try Fira Code.

from operator-mono-lig.

@kiliman I'd be willing to help add/create some of these others font weights, too, but I could not figure out how to export them into XML files needed. What am I missing?

from operator-mono-lig.

@kennyklee Awesome. Glad you were able to figure out how things are organized. I'll actually have true Book weight ligatures shortly, so they won't look out of place with the rest of the font.

from operator-mono-lig.

@kiliman Thanks for the great work! Looking forward to the Book weight. Any chance you could add the Light weight as well any time in the future?

from operator-mono-lig.

I have completed the following weights:

ScreenSmart version

• Operator Mono ScreenSmart Book
• Operator Mono ScreenSmart Book Italic
• Operator Mono ScreenSmart Medium
• Coming Soon Operator Mono ScreenSmart Medium Italic

Regular version

• Operator Mono Medium
• Operator Mono Medium Italic

I've streamlined the process for generating the ligatures so I should be able to get the rest of the font weights completed this weekend. Thanks for your patience.

from operator-mono-lig.

There appears to be a slight issue with the font name tables, however they do install.

I'll take a look at it in the morning.

from operator-mono-lig.

Ugh. Hold off on installing this version. Something isn't right. I'll take a look in the morning.

from operator-mono-lig.

Making some progress this morning.

Looks like the ligatures with 3 components are not working. I'm wondering if ordering is important. Also, none of the italic ligatures are working for some reason 😢

Anyway, here's a screenshot for the Book weight. It actually looks really nice.

from operator-mono-lig.

Apparently order does matter! Now to figure out what's wrong with the italics.

from operator-mono-lig.

In my Glyphs version of the font, the italic ligatures (except for the html comment start) are working, so must be an issue with the extraction/build.

from operator-mono-lig.

Ok, I've fixed the issues with Windows, however still can't get italics to work.

I'm going to close this issue and create a new issue for italics.

Please try this out and let me know if you have any problems.

Thanks!

from operator-mono-lig.

Not sure whether this belongs into this issue, but this is what happened when I built the ScreenSmart versions and installed them on macOS 10.12.6, the glyphs seem to lose their correct width:

Loading them into the http://www.glyphrstudio.com/online/ tool shows the same problem:

Checking the "auto calculate" checkbox changes the right border:

Which has an effect when loading the resulting front in the system's font program:

Without the correct glyph width, the result looks like this:

I have attempted to fix the problem myself but can't find out where in the process the glyph width gets lost :(

Debugging info: I am using node v8.2.1, python 2.7 and fonttools 3.15.1.

Edit: In any case, thanks for your work on this project!

from operator-mono-lig.

@iStefo Thanks for the detailed bug report. Can you pull latest and rebuild the fonts?

I'm not seeing what you're seeing. Just remember, for the ScreenSmart versions, I only have Book/Book Italic and Medium (no italic yet).

As you can see from the screenshots (Operator Mono SSm Lig Medium), VS Code is synthesizing italics (you get the slanted ligatures, but also slanted character, not true italics).

If you're still having problems, can you create a new issue?

Thanks!!

from operator-mono-lig.