-
Notifications
You must be signed in to change notification settings - Fork 33
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
Unicode Block "Miscellaneous Symbols and Arrows" support #12
Comments
I have plans to add a large part of the Arrows Unicode block. From there, I suppose it wouldn't be too difficult to add at least the arrows from the Miscellaneous Symbols and Arrows Unicode block, where the two characters you pointed out are located. On a more general note, I don't consider Spleen done yet and plan to keep on adding more characters. |
@kucharskim It's been a while, but I would appreciate if you could point out which programs use those characters so I can test the results. Maybe adding the most used arrows would not be that much work, I will be working on that. |
@fcambus I saw it initially with https://github.com/near/nearcore/ but in general the new blockchain industry is full of emoji and utf-8 in the application logs. I saw non-ASCII characters in substrate chains (https://github.com/paritytech/polkadot), I don't remember does https://github.com/ethereum/go-ethereum also have some non-standard (as in, non-ASCII) characters. This task specifically was triggered by nearcore. |
@kucharskim Thanks for the info, I started working on adding some arrows already, will commit more stuff during the following weeks. |
Closing this as the mentioned symbols have been added last year. |
Yes, indeed it works (copy paste from XTerm):
Thanks Frederic! |
Are you planning to add support to Spleen for something like that? I'm asking as recently found some apps which on the console are using up/down arrows for download and upload indication:
⬇ ⬆
\xe2\xac\x87 \xe2\xac\x86
U+2B07 U+2B06
and was wondering is this Unicode block on your roadmap or maybe not?
The text was updated successfully, but these errors were encountered: