Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Symbols as █▓▒░ don't join vertically #103

Closed
h-h-h-h opened this issue Aug 15, 2015 · 3 comments
Closed

Symbols as █▓▒░ don't join vertically #103

h-h-h-h opened this issue Aug 15, 2015 · 3 comments

Comments

@h-h-h-h
Copy link

h-h-h-h commented Aug 15, 2015

Hello,

the symbols listed in the title and similar ones don't join vertically while box drawing symbols like │║ do.

These fonts do join them in both directions:

  • Consolas
  • Lucida Console
  • Courier New

Test text:

│██▓▓▒▒░░║
│██▓▓▒▒░░║
│██▓▓▒▒░░║
│██▓▓▒▒░░║
│██▓▓▒▒░░║
│██▓▓▒▒░░║
│██▓▓▒▒░░║
│██▓▓▒▒░░║
│██▓▓▒▒░░║
│██▓▓▒▒░░║

Having these symbols joined vertically would be useful, e.g., for seamless bar graphs. If you want seamed bar graphs, there are symbols with a shorter height useful for that purpose.

@frankrolf
Copy link
Member

This issue has been mentioned a couple times before, it really depends on the environment if those characters overlap or not.

Nevertheless, I think I finally have an idea how to fix this. The challenge is aligning the diagonal, cross-hatched pattern in a way that it is seamless.

Right now, they will align when you set your line distance to the point size (compressed setting, e.g. 10 on 10pt).

I will modify the pattern in a way that it will match for even values, e.g. 10 on 12 pt, 10 on 14pt and so forth.

@h-h-h-h
Copy link
Author

h-h-h-h commented Aug 15, 2015

Here on GitHub I see line spacing, but in Windows' Notepad there's no line spacing so the box drawing symbols build a solid line. The other symbols, however, build gaps on the y-axis in Notepad. Isn't this an issue of the character shape (the black rectangle height)?

If you are speaking of some font design internals, however, it would be great to just hear that this will solve the issue.

@frankrolf
Copy link
Member

Duplicate of issue #57.
Tracking the progress in original issue and closing this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants