This design feature is felt to improve legibility because it "opens up" features of these lowercase shapes that can become difficult to visualize in poor viewing conditions. With larger x-heights, the lowercase glyphs are larger. This is the ~height of the lowercase glyphs in the sets (approximate because many lowercase glyphs extend beyond the baseline or above the x-height 'line', the x is a good measure because it has horizontal lines at the top and bottom of the strokes that are used to create the glyph). Take this into consideration once this script is released if you commonly use these glyphs in the body of text where you use Markus, the x-height is a different property of the fonts. This has been part of my hesitation with the multi-variant releases because we are still working on the spacing / orientation of these vertical positions in the main font set. Anything that requires exact vertical spacing relationships across different lines (including the box drawing glyphs and block element glyphs) will no longer maintain these relationships with these adjustments. If there are a couple of tighter and looser variant specs that seem to be in common use, then perhaps we could consider including these changes as part of the build workflow.Īny default vertical spacing changes create issues for the fonts that are very time consuming to correct. We've had the discussion about releasing separate (from the main release builds) builds that include tighter and looser spacing defaults, but I think that this will be the most flexible approach. This will work in both directions so that you can modify the defaults either tighter or looser based upon your platform/editor combination. I've kicked this around for some time and what I intend to do is provide a script that allows you to define the spacing for yourself in the fonts.
#Otf vs ttf slingshot code
It's not the case for many/most source code text editors which creates the issue. With typesetting, this isn't an issue because you can define it however you would like, irrespective of the font defaults. Some want to pack as many possible lines of code into a given view (there was a comment that one person wanted it "clown car tight" :) ), others want greater legibility associated with more whitespace between rows of characters. It's a very subjective issue and there will not be a one size fits all solution. There are some who would like to see it tighter still and others who have requested more default spacing between lines. We originally began with a wider line spacing and it narrowed over the first few iterations of the v2.x font releases. space between two rows of glyphs) have been all over the place.
0 kommentar(er)
