You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have in recent years been frustrated with the fact that I cannot use braille characters in the default windows terminals, but I am really excited to see that this font supports braille. I immediately went to the blessed-contrib repository, a NodeJS module that uses braille characters for displaying dashboard information, and ran the demo file, it did mostly work.
It seems there are a few glitches which I suspect is because not all braille characters are supported.
If these defects could be fixed that would be tremendously helpful.
If you would like to run the demo for yourself, you can check out the blessed-contrib repository and look at the instructions to run the demo, it's pretty straight forward.
The text was updated successfully, but these errors were encountered:
Actually, the font does not at current support any Braille characters and, at least in your screenshot, it looks like you're using a different font. We can certainly add them to the list of symbols to support though!
Description of the new feature/enhancement
I have in recent years been frustrated with the fact that I cannot use braille characters in the default windows terminals, but I am really excited to see that this font supports braille. I immediately went to the blessed-contrib repository, a NodeJS module that uses braille characters for displaying dashboard information, and ran the demo file, it did mostly work.

It seems there are a few glitches which I suspect is because not all braille characters are supported.
If these defects could be fixed that would be tremendously helpful.
If you would like to run the demo for yourself, you can check out the blessed-contrib repository and look at the instructions to run the demo, it's pretty straight forward.
The text was updated successfully, but these errors were encountered: