-
Notifications
You must be signed in to change notification settings - Fork 84
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
Printable ASCII characters >=128 show up on Latin1 terminals as <xx>
#508
Comments
h3xx
changed the title
Formerly printable characters fail to show up on Latin1 terminals (LANG=en_US)
Printable ASCII characters >=128 show up on Latin1 terminals as May 15, 2024
<xx>
Thanks, fixed in d5bf864. |
Confirmed fixed! Thanks for the quick turnaround. 😄 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On non-UTF8 terminals, the entire range of printable ASCII extended characters >= 128 (0x80) is replaced with
<xx>
wherexx
is the hex code -- regardless of whetherLESSCHARDEF
flags them as printable.They displayed properly until recently.
I already did some of the legwork tracking this down using
git bisect
.I'm fairly certain commit a60cc1b introduces this regression. (2024-04-23 "Fix bug in control_char().")
Steps to Repro
ïðñòóôõö÷øùúûüýþÿ
because they're in the printable range set byLESSCHARDEF
. They displayed properly in less v653 and all git versions up until the commit mentioned above.<EF><F0><F1><F2><F3><F4><F5><F6><F7><F8><F9><FA><FB><FC><FD><FE><FF>
shows.The text was updated successfully, but these errors were encountered: