4 ms·

Not trying to be negative, just confused: I don't really see how this font is "designed for symbol-heavy languages". The symbols look normal to me. Maybe the

Not trying to be negative, just confused: I don't really see how this font is "designed for symbol-heavy languages". The symbols look normal to me. Maybe the letters are a little more spaced? I'd love to be enlightened.

floppyd 11mo ago
>Near-Perfect Alignment: multi-character symbols like ->, >>=, =~, :: align seamlessly The GitHub page has a list with 5 items of what was the focus, this is the first (and I think the most easily noticeable) area
- layer8 11mo ago
  I wonder why only near-perfect.
  - _piud 11mo ago
    there are bounds to be many many operators and glyph combinations where things don't match properly. an example is the variable declaration and initialisation symbol in Go which combines colon and equal sign. if you use Myna and come across any such examples, please raise a feature request. i only focused on glyphs for languages i use personally. but if there is interest i am open to adding contextual alternates to give some alignment in cases where changing one glyph would disturb other combinations. of course you can always point out any rendering or design issues with singular glyphs too.
_piud 11mo ago
designer here. by symbol-heavy languages i mean languages like Perl and Haskell which make heavy use of symbols (sigils in Perl and operators in Haskell). Myna was designed after my frustration with other monospace fonts combined with my (self-imposed) inability to use ligatures.
- Avshalom 11mo ago
  Apl, BQN and Oiua would like to talk to you.
  - andrewl-hn 11mo ago
    And some proof assistant languages and frameworks. For a second I was really excited there, but this is another font with “programming ligatures”.
    - _piud 11mo ago
      i know the title can be a bit misleading but Myna is primarily ASCII. languages which insist on using full Unicode like APL and Agda have bigger problems (availability of uniform glyphs and inconsistency with monospace design) on their plates. which imo is one reason why full Unicode editing hasn't really caught up. Myna doesn't use any ligatures though. it would run on almost all terminals and editors.
      - andrewl-hn 11mo ago
        Yeah, I realize that I was wrong about ligatures afterwards. The two plusses next to each other looked as if they are a single combined glyph, but they are in fact separate. I think this is the effect you were trying to reach, and it looks very slick.
      - agarttha 11mo ago
        What about a J example? https://code.jsoftware.com/wiki/NuVoc https://code.jsoftware.com/wiki/NuVoc
        ofalkaed 11mo ago
        J mostly looks good but [) looks almost like a fancy capital D which can be distracting and =# run together at smaller font sizes which is a little weird. Those are the only things that jump out at me but I did not look hard, overall I would say it is one of the better fonts I have tried for J. The big problem that I am having with this font is that its narrowness makes it difficult to find a fallback font for APL/BQN that plays well.
eviks 11mo ago
That's because the proper way to explain design differences is by showing them, and there is no comparison, so of course it's easy to get confused

floppyd 11mo ago

>Near-Perfect Alignment: multi-character symbols like ->, >>=, =~, :: align seamlessly The GitHub page has a list with 5 items of what was the focus, this is the first (and I think the most easily noticeable) area

layer8 11mo ago
I wonder why only near-perfect.
- _piud 11mo ago
  there are bounds to be many many operators and glyph combinations where things don't match properly. an example is the variable declaration and initialisation symbol in Go which combines colon and equal sign. if you use Myna and come across any such examples, please raise a feature request. i only focused on glyphs for languages i use personally. but if there is interest i am open to adding contextual alternates to give some alignment in cases where changing one glyph would disturb other combinations. of course you can always point out any rendering or design issues with singular glyphs too.

_piud 11mo ago

designer here. by symbol-heavy languages i mean languages like Perl and Haskell which make heavy use of symbols (sigils in Perl and operators in Haskell). Myna was designed after my frustration with other monospace fonts combined with my (self-imposed) inability to use ligatures.

Avshalom 11mo ago
Apl, BQN and Oiua would like to talk to you.
- andrewl-hn 11mo ago
  And some proof assistant languages and frameworks. For a second I was really excited there, but this is another font with “programming ligatures”.
  - _piud 11mo ago
    i know the title can be a bit misleading but Myna is primarily ASCII. languages which insist on using full Unicode like APL and Agda have bigger problems (availability of uniform glyphs and inconsistency with monospace design) on their plates. which imo is one reason why full Unicode editing hasn't really caught up. Myna doesn't use any ligatures though. it would run on almost all terminals and editors.
    - andrewl-hn 11mo ago
      Yeah, I realize that I was wrong about ligatures afterwards. The two plusses next to each other looked as if they are a single combined glyph, but they are in fact separate. I think this is the effect you were trying to reach, and it looks very slick.
    - agarttha 11mo ago
      What about a J example? https://code.jsoftware.com/wiki/NuVoc https://code.jsoftware.com/wiki/NuVoc
      - ofalkaed 11mo ago
        J mostly looks good but [) looks almost like a fancy capital D which can be distracting and =# run together at smaller font sizes which is a little weird. Those are the only things that jump out at me but I did not look hard, overall I would say it is one of the better fonts I have tried for J. The big problem that I am having with this font is that its narrowness makes it difficult to find a fallback font for APL/BQN that plays well.

eviks 11mo ago

That's because the proper way to explain design differences is by showing them, and there is no comparison, so of course it's easy to get confused