3 ms·
The problem with using braille characters is the spacing which leaves to uneven distribution of "pixels". This could be improved by using octants, which will be
by chaz6 2y ago
The problem with using braille characters is the spacing which leaves to uneven distribution of "pixels". This could be improved by using octants, which will be included in Unicode 16.
https://www.unicode.org/charts/PDF/Unicode-16.0/U160-1CC00.pdf https://www.unicode.org/charts/PDF/Unicode-16.0/U160-1CC00.p...
- jmholla 2y agoI don't see a completely filled in octant. What character should be used for that?
- vok 2y agoWith the right font (e.g. http://viznut.fi/unscii/ http://viznut.fi/unscii/) and line spacing, braille characters work fine with an even distribution of pixels and no gaps.
- apitman 2y agoThat's pretty cool. Are there any terminals that ship with such a setup? Better yet, is it possible to override this behavior in your app? For example, could I make a TUI app specifically for plotting data, and have it select it's own font that's optimized for braille plotting?
- sp332 2y agoThe new Cascadia Code update has both braille and octants. https://devblogs.microsoft.com/commandline/cascadia-code-2404-23/ https://devblogs.microsoft.com/commandline/cascadia-code-240...