search

microsoft / cascadia-code

This is a fun, new monospaced font that includes programming ligatures and is designed to enhance the modern look and feel of the Windows Terminal.
Other
25.39k stars 803 forks source link

Documentation Issue #533

Closed JAYD3V closed 3 years ago

JAYD3V commented 3 years ago

So its not an issue with a specific document, but rather an issue with the version number. I never really seen anything that uses a versioning system quite like the one that Cascadia Code implements. To be completely honest,I don't really understand it, but that isn't what bothers me.

What I don't get is this:

I downloaded Version 2106.17, in the documentation, the link I clicked on (as I am certain you know already) read "2106.17", although, my GNU font manager, shows the Cascadia Code Version as being 2106.02. I don't really care, if the versions don't match, because the font works, but I do care about any differences that exist between the two versions, and if there exist a 2106.01, 2106.03, 2106.04, 2106.18, or maybe there's a 2106.12345. So whats the difference, and why is it showing as 2106.02 on my machine?

DHowett commented 3 years ago

2106.02 is unexpected! I wonder where it's getting that.

The Cascadia family is versioned by the year, month and day. 2106.17 was completed on 2021-06-17.

aaronbell commented 3 years ago

The version string in the font is 2106.017 so it is likely just rounding to 2106.02 in your tool. @Dhowett, we might want to keep that in mind 😒

JAYD3V commented 3 years ago

Tool's Name: "GTK+ Font Manager 0.8.6" Tool's Version: "0.8.6" Platform: "Ubuntu 21.04"


Here's a Screenshot:

Cascadia-Code__Version-Issue

JAYD3V commented 3 years ago

Oh ya, good thinking Mr. Bell, it probably is rounding off.