This, like many fonts, fails to handle vertical arrows: | ^ v | Note that the raised appearance of `^` exists for compatibility with typewriters that use the backspace key to use it as a circumflex accent over lowercase letters. This is doubly obsolete today (we have real combined characters and can use them on uppercase). This is one of those cases where the name originally used for the character in various standard…
> Note that the raised appearance of `^` exists for compatibility with typewriters that use the backspace key to use it as a circumflex accent over lowercase letters. This is doubly obsolete today The origins don’t really matter at this point. That’s what the character looks like and it’s what everyone expects. Your use case is extremely niche. Making a font choice for that specific double-line situation would aliena…
Myna: Monospace typeface designed for symbol-heavy programming languages
111–120 of 185 posts
Re: Myna: Monospace typeface designed for symbol-heavy programming languages
#112My favorite monospace font is "Ubuntu Mono" for ages. As an engineer, I like to see -- for the lack of better word -- some taste instead of characters being too formal and too symmetric. Ubuntu and Ubuntu-Mono satisfy this to a good extent without being too much, like in comic sans. The closest font with similar taste, which I found recently is Mononoki
Re: Myna: Monospace typeface designed for symbol-heavy programming languages
#113Also see the JuliaMono typeface: https://juliamono.netlify.app It was designed to be a comprehensive monocode typeface to support Julia's full Unicode support.
Re: Myna: Monospace typeface designed for symbol-heavy programming languages
#114I don't know why "->" should render as an arrow when we could just use an actual Unicode arrow. If need be, have macros for your editors that allow you to convert the "->" into an actual arrow.
Unicode is not there for you to necessarily use the whole thing. It's there so that everyone in the world can encode their text the same way, despite having a completely different set of characters on their keyboards.
Re: Myna: Monospace typeface designed for symbol-heavy programming languages
#115Earlier quoted context omitted.
> have macros for your editors that allow you to convert the "->" into an actual arrow. Or, as suggested here, use language macros: #define → -> https://lists.isocpp.org/std-proposals/2023/01/5485.php
This is not valid C, though. The characters allowed for identifiers are defined in Unicode Standard Annex #31, and those easily understood as operators, like arrows, are not included.
Re: Myna: Monospace typeface designed for symbol-heavy programming languages
#116Genuine question: is everyone coding on such high resolution displays and/or with font sizes so big nowadays? For me, the example screenshots are useless to see how the font would actually look like in my editor.
Re: Myna: Monospace typeface designed for symbol-heavy programming languages
#117Very nice and condensed. The same reason I switched to Iosevka ( Joseph ), recently: https://github.com/be5invis/Iosevka The fun thing with Iosevka is that one stands a reasonable chance of reading the source code (as opposed to just random numbers in SplineSets etc.)
Switched from Iosevka to this, feels a little more readable.
Re: Myna: Monospace typeface designed for symbol-heavy programming languages
#118> Are you frustrated that -> looks nothing like an arrow The proper solution is, of course, to allow ←arrows→ (and, naturally, not trying to fit a variable peg into a monowidth whole)... maybe in the next generation of languages when the bottom level of typesetting quality is raised a bit
i have addressed this in one of the other comments. it is impossible to achieve both elegance (good look) and consistency (monospace width) in these cases. many folks, like yourself, are pioneering full Unicode editing. we, on the other end, are just trying to make editing without ligatures elegant because ASCII, i believe, would remain predominant for a long time to come.
Re: Myna: Monospace typeface designed for symbol-heavy programming languages
#119Earlier quoted context omitted.
This is not valid C, though. The characters allowed for identifiers are defined in Unicode Standard Annex #31, and those easily understood as operators, like arrows, are not included.
Unless you extend the language reference beyond the limits of #31, of course
Re: Myna: Monospace typeface designed for symbol-heavy programming languages
#120Earlier quoted context omitted.
i have addressed this in one of the other comments. it is impossible to achieve both elegance (good look) and consistency (monospace width) in these cases. many folks, like yourself, are pioneering full Unicode editing. we, on the other end, are just trying to make editing without ligatures elegant because ASCII, i believe, would remain predominant for a long time to come.
well, my "pioneering efforts" :) are killed by language designers, as you note "it is impossible", so we can only waste time looking for various workarounds like using fonts designed around those limits...
what would be ideal is a variable-width font which covers most Unicode characters consistently. some Unicode characters (eg, arrow) would need space of 2 characters and so on. making it elegant would require quite a lot of work to ensure Unicode does't look out of place (eg, arrow in your comment).
these are the problems which make me feel full Unicode editing is difficult to achieve in the short run. not to mention the obvious issue of typing Unicode characters from the ASCII keyboard.
i've included a reasonable subset of Unicode in Myna but it may not look very good. don't get me wrong, i appreciate the Unicode advocacy. but until we've something good-looking and well-behaving tooling on that side, using it would be quite frustrating.