Suggestion: can you support light versions also? about operator-mono-lig HOT 23 CLOSED

Yes, I plan on adding all the weights. I'm working on Operator Mono Book (non-ScreenSmart) now. I'll then start on Light (ScreenSmart and regular).

from operator-mono-lig.

@vikky49 Did you pull the latest version of the code?

If you run the build command it will try to build a font for every font that's defined in the ligature folder that you have in the original folder.

What's probably happening is that you don't have the ScreenSmart version of the Book weight. I haven't created the ligatures for the regular Book weight yet. I'm working on it now.

from operator-mono-lig.

I've started on Operator Mono SSm Light. Here's the regular version. Need to finish the italic.

Here's Operator Mono SSm Light at 14px in Visual Studio Code.

Note: I also added the F# fish operators >=> and <=<

from operator-mono-lig.

Just letting you know there's still interest in the light versions!

Using the book version right now and it's great with ligatures. 🎉

from operator-mono-lig.

Starting work on Operator Mono Light (the #2 weight on the poll). Sorry for the delay everyone.

These are all redone from scratch with the new process (see features/contextualsubst) branch.

These ligatures have more consistent spacing and better hints for smaller sizes.

Ignore the italics in the screenshot. Since I haven't started the italic version, VS Code is synthesizing italics from the regular style.

from operator-mono-lig.

wonderful, Thank you so much.. waiting for it. :) 👍

from operator-mono-lig.

@kiliman Looking forward to the light and extra light versions of the non-smartscreen versions. These should have been in the original font from the start! Thanks a bunch for doing these!

from operator-mono-lig.

I pushed Operator Mono SSm Light. I'll push the italic version out as soon as I can.

Enjoy!

from operator-mono-lig.

Wow, that was fast. Thanks a lot!

from operator-mono-lig.

Would also like the non-smartscreen version of light, when you get a chance.

from operator-mono-lig.

The new branch only contains Operator Mono SSm Book for now.

I should be finished with Operator Mono Light this weekend. I just wanted to let you know that I was finally back to working on the ligatures.

from operator-mono-lig.

Can't say enough about how great this tool is! Fine work. 🚀

I too would love the light non-smartscreen versions. It must be good deal of work. I wish I could help out.

from operator-mono-lig.

Build worked great.
Ligs look awesome.
Smart hitting the common ligs first - doubles ==, !=, =>

from operator-mono-lig.

First of all, thank you for working on the ligature support for Operator Mono! Super cool!
I look forward to the completion of Operator Mono Lig Light with support for === !== 😀

from operator-mono-lig.

@kiliman How do i build the fonts for just the Book and Book Italic .By default its only building the Medium and Medium Italic fonts

from operator-mono-lig.

Thanks for the tool @kiliman! It's awesome!

Is there any progress with the light version? Maybe we can help you somehow?

from operator-mono-lig.

@kiliman Any progress on the italic version?

from operator-mono-lig.

@kiliman
./build.sh does not appear to do anything.

• pulled branch features/contextsubst
• npm install for good measure
• used both node v8.10.0 and v9.8.0

Running ./build.sh in terminal completes sub-second and produces no output.

from operator-mono-lig.

Pushed initial version of Operator Mono Light to branch. It doesn't have all the ligatures but I wanted to verify the extract and build process for a second font.

Let me know what you think.

from operator-mono-lig.

Using Gitbash with all the linuxy things on Win 10 ./bash.sh runs, but I'm getting the following.
Parsing 'DSIG' table... ERROR: Unhandled exception has occurred

Somethings not playing nicely with fonttools on my setup for this branch. I'll look into it more tonight when I have time.

from operator-mono-lig.

I don't have the Linux subsystem installed, but I'm able to build from Windows 10.

Can you tell me what versions you have for Python and fonttools?

from operator-mono-lig.

Not using the subsystem, it's a little too flakey for me at this point.

What I am using is the really good optional Unix tools integration in the latest git-scm builds for Windows.

Python 2.7.14 ,fonttools 3.25.0, node 8.11.1

I'll be upgrading python to 2.7.15 and if that doesn't work I'll move over to 3.6.5 and let you know if anything changes.

Update: I've got it working with a refreshed install of Python 2.7.15

from operator-mono-lig.

light version is not build

from operator-mono-lig.