Not all chars are rendered monospaced

zingmane commented 6 months ago

Some characters are not rendered mono spaced, especially those created with ascii drawing generators (e.g. https://asciiflow.com). It's not an issue with ligatures.

vscode settings:

"editor.fontFamily": "'Monaspace Neon', monospace",
"editor.fontLigatures": "'calt', 'liga', 'dlig', 'ss01', 'ss02'",

The example is this:

 *       ┌───────┐  ┌───────┐  ┌───────┐  ┌───────┐  ┌───────┐  ┌───────┐  ┌───────┐  ┌───────┐
 *       │       ├──┤       ├──┤       ├──┤       ├──┤       ├──┤       ├──┤       ├──┤       │
 *       └───────┘  └───────┘  └───────┘  └───────┘  └───────┘  └───────┘  └───────┘  └───────┘

cormullion commented 6 months ago

When you save a drawing in AsciiFlow there are two options: AsciiExtended and AsciiBasic. AsciiExtended (which should be named Unicode, probably) saves the drawing as Unicode glyphs in the U+2500 block, the "box drawing" characters.

If the font you're using doesn't contain these U+25.. box drawing characters, most applications will find a replacement font that does, and use the glyphs from that one. This process is called "font fallback".

But some terminals and editors handle the different metrics of the different fonts more carefully than others. Unfortunately I think VS-Code 'faithfully' keeps using the different metrics of each font, and so you can see the slowly increasing width differences accumulating over the length of line 192 in your screenshot, as the glyphs from each font are chosen.

githubnext / monaspace

Not all chars are rendered monospaced #174