-
Notifications
You must be signed in to change notification settings - Fork 28
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
UTF-8 (rather, any non-ASCII) evidently dropped/ignored #26
Comments
I can confirm this problem. It happens for a single unicode character such as |
Note also that some chinese characters cause an error to be reported by the parser "New state of 'nil' is invalid", eg replacing the above main with this one
Gives
|
#2501 This bug causes lots of strange behaviour with non-ASCII characters and --progress Azure/go-ansiterm#26
#2501 This bug causes lots of strange behaviour with non-ASCII characters and --progress Azure/go-ansiterm#26
#2501 This bug causes lots of strange behaviour with non-ASCII characters and --progress Azure/go-ansiterm#26
This issue celebrates a 3 years anniversary π€ |
Yes. On the other hand, 6 days ago we celebrated the 5 year anniversary of a Windows release with built-in VT support. So as painful as it is for users stuck on even older versions of Windows, it's unlikely that we'll make any significant improvements to this package. |
Steps to reproduce:
Parse, for example, π¨βπ©βπ§βπ¦
Expected: constituent UTF-8 bytes of the four unicode characters, and the three unicode zero-width join characters, should all be send to Print.
Actual: handler.Print is not called. No other method appears to be called.
The text was updated successfully, but these errors were encountered: