But this requires more work (and thus cost and time) up-front.Д¬ascadia Code, gives you a good example of one of our most recently created, and open-source fonts, and for which we have bold goals. that modern font engines can then interpolate-between to render at variable weights etc. We prefer TrueType/OpenType vector fonts because they're scalable, adjustable, can be rendered by a GPU, etc.Д«etter still would be variable fonts defined by vectors at a few intermediate weights etc. Trying to make a bitmap font that can scale correctly across the enormous gamut of screens and resolutions that we have to support in legacy, current, and future devices would be 'difficult', to put it politely рџњ I could contribute to this too, especially to font design and composer algos. If it would be an open source font storage format, everyone could contribute fonts and edit them. And for bigger sizes the renderer could just switch to some existing vector font, as it works now. In case of bitmap approach, I'd say creating 3-4 different sizes would cover most needs for 100-200 PPI displays.

3 weeks of one man's work.Д«ut creating a vector font, jiggling the vector paths and hinting may take 10x more time.Д®specially trying to achieve the detail level and feel of a finely crafted font, it may take forever.ДЄfter all, it's only a question of scalability. I would suggest to make the text renderer that can directly use bitmap font by specific sizes.ДЄn example: to create graymaps for one size, Latin set, and to optimize it's quality/readability may take ca. This would eliminate the pain of creating of fine fonts in the first place. To my understanding, to make life easier, what one want is support for grayscale bitmap fonts aka 'graymaps'. I dealt a lot with font related things, and I am curious about it.Д«TW, I wonder why for this specific case (terminal) one would desire a vector font? is a laborious, costly and complex subject area, but do know that we are working hard to figure out a decent story moving forward. Thanks for yor comments as well and good luck with the project!ДЄlas, font licensing, creation, hinting, etc. make them wider, like in CourierДЄlso note that inter-line spacing affects readability, it would be nice to have an option to adjust the line spacing.

center all signs to lowercase (><=*- etc.).

make it slightly bolder (doing it properly in vector actually is long and painful story).

So if I would do the job, I'd do following: But regardless, glyph proportions are too wide, and the design is on the 'grotesque' side which makes it less readable than SimSun. I feel it is initially designed for monospace usage. It has slightly better glyph spacing (see 'i', 'l').

And most signs are centered to caps instead of being centers to lowercase letters, which is a drawback.

glyhps 'i', 'l', 't' should have been morphed to cover more space, like in Courier. It has better glyph proportions, Times-like (a bit narrowed, which is a plus) and details, but there are some glyphs not optimized for the monospace usage, e.g. Though, both have common issue - originated from print typefaces, thus appear too thin on screen (unless theres some tricky hinting). In terms of readability, best monospaced font (preinstalled with Windows) I've seen so far is SimSun. Started using the Terminal recently and came across this interesting discussion, just want to insert my opinions.

Ms mingliu font