[screen-devel] [bug #55138] Bug: UTF-8 characters in hardstatus not working

2019-05-23 Thread Stefan Assmann
Follow-up Comment #18, bug #55138 (project screen): Part of the problem seems to be that FromUtf8() interprets UTF8 bytes incorrectly due to a signedness issue. For example: ¢ (U+A2) This 2-byte UTF8 character gets interpreted as ffc2 ffa2 instead of c2 a2 A dirty hack to demonstrate this

[screen-devel] [bug #55138] Bug: UTF-8 characters in hardstatus not working

2019-02-21 Thread Nicolas Schodet
Follow-up Comment #17, bug #55138 (project screen): I had a look to see if I can come with a temporary solution… but I am afraid any change will break something else… ___ Reply to this item at: ___

[screen-devel] [bug #55138] Bug: UTF-8 characters in hardstatus not working

2019-02-18 Thread Elof
Follow-up Comment #16, bug #55138 (project screen): Just a response to Nicolas, Unfortunetly I need the window title dynamic in the hardstatus line, so it can't be statically assigned. (and the window titles themselves must be in UTF-8, otherwise the problem is just moved from the hardstatus lin

[screen-devel] [bug #55138] Bug: UTF-8 characters in hardstatus not working

2019-02-18 Thread Nicolas Schodet
Follow-up Comment #15, bug #55138 (project screen): Handle everything using characters instead of byte is the sane way, for sure! Note there can still be problems with combining chars, clusters, or emoticons. To Elof, I noticed that I do not have the problem if I define the string in .screenrc,

[screen-devel] [bug #55138] Bug: UTF-8 characters in hardstatus not working

2019-02-17 Thread Amadeusz Sławiński
Update of bug #55138 (project screen): Status:None => Duplicate ___ Follow-up Comment #14: It's well known deficiency, there is quite few similar bug reports: 24208 hardcopy doesn't han

[screen-devel] [bug #55138] Bug: UTF-8 characters in hardstatus not working

2019-02-17 Thread Nicolas Schodet
Follow-up Comment #13, bug #55138 (project screen): OK, I just tried with xterm and I can see the problem… weird… Now I can debug this, thanks! ___ Reply to this item at: _

[screen-devel] [bug #55138] Bug: UTF-8 characters in hardstatus not working

2019-02-17 Thread Elof
Follow-up Comment #12, bug #55138 (project screen): Both outside and inside screen, 'echo å | xxd' result in: : c3a5 0a ... Yes, in Debian 9 the default screen is 4.5.0 but since it has the hardstatus problem I compiled 4.6.2 to see if it was fixed. Do you mean that you can't

[screen-devel] [bug #55138] Bug: UTF-8 characters in hardstatus not working

2019-02-17 Thread Nicolas Schodet
Follow-up Comment #11, bug #55138 (project screen): Thanks for your tests. Can you run without running screen: echo å | xxd Where does your screen come from, I have debian 9 here and it's screen 4.5.0. Can you run: dpkg -l screen Thanks, sorry for so many questions, I just want to be ab

[screen-devel] [bug #55138] Bug: UTF-8 characters in hardstatus not working

2019-02-16 Thread Elof
Follow-up Comment #10, bug #55138 (project screen): Attachments 2 and 3 were swapped in my last post, so pic 3 show the hardstatus string "å". Those three examples were from screen v4.5.0 (Debian 8). Continuing with the tests on screen 4.6.2 (Debian 9): Pic 1 show the same problem as in 2.5.0

[screen-devel] [bug #55138] Bug: UTF-8 characters in hardstatus not working

2019-02-16 Thread Elof
Follow-up Comment #9, bug #55138 (project screen): Hi! Pic 1 show how everything is looking great as long as there's no åäö in the statusline. Pic 2 show the hardstatus string "å" Pic 3 show how the contents of the screen is moved one line up every time the clock in the right corner is updated.

[screen-devel] [bug #55138] Bug: UTF-8 characters in hardstatus not working

2019-02-15 Thread Nicolas Schodet
Follow-up Comment #8, bug #55138 (project screen): Hej! I am not sure I was clear enough, can you try this (using "^A :" to enter command): hardstatus string "å" And show us a screenshoot? Can you try from a fresh screen started with -U? Can you send the output of the "locale" command? Can y

[screen-devel] [bug #55138] Bug: UTF-8 characters in hardstatus not working

2019-02-14 Thread Elof
Follow-up Comment #7, bug #55138 (project screen): Hi Nicolas! Yes, confirmed. As long as I use plain us-ascii chars, everything is OK everywhere. In screen windows, in the screen window-list and in the hardstatus line. When I use Swedish characters (like: Räksmörgås), they are displayed correct

[screen-devel] [bug #55138] Bug: UTF-8 characters in hardstatus not working

2019-02-14 Thread Nicolas Schodet
Follow-up Comment #6, bug #55138 (project screen): Hello, On my system, I can not fully reproduce the problem, with screen 4.5.0, 4.6.2, nor with master branch, the character are always printed correctly. However, I can see a problem with the padding computation (%=) on the v4 branch, and a prob

[screen-devel] [bug #55138] Bug: UTF-8 characters in hardstatus not working

2018-12-28 Thread Elof
Follow-up Comment #5, bug #55138 (project screen): No takers on this? 99.9% of screen is already UTF-8 compatible, we just need that last 0.1% fixed. :-) ___ Reply to this item at: ___

[screen-devel] [bug #55138] Bug: UTF-8 characters in hardstatus not working

2018-12-02 Thread Elof
Follow-up Comment #4, bug #55138 (project screen): I just managed to patch the 4.6.2 source. Unfortunetly, neither of the two patches below solved my problem. Both of them gave the same result: Before: Swedish chars in the statusline are shown as grey rectangular blocks. After: Swedish chars in

[screen-devel] [bug #55138] Bug: UTF-8 characters in hardstatus not working

2018-11-30 Thread Elof
Follow-up Comment #3, bug #55138 (project screen): ...or this fork made 29 Dec 2016: https://gist.github.com/yoshikaw/10586719 ___ Reply to this item at: __

[screen-devel] [bug #55138] Bug: UTF-8 characters in hardstatus not working

2018-11-30 Thread Elof
Follow-up Comment #2, bug #55138 (project screen): Hi Mike. Sorry to hear that. This old patch doesn't just happen to work? https://gist.github.com/saitoha/3143922 I'm no developer, so I don't know how to patch the source and try it out myself, but maybe you could just throw 20 minutes on it? It

[screen-devel] [bug #55138] Bug: UTF-8 characters in hardstatus not working

2018-11-30 Thread Mike Gerwitz
Follow-up Comment #1, bug #55138 (project screen): Indeed, this is something that I had set out to fix a number of years back. I did a bunch of refactoring to clean up the hardstatus code, but didn't have time to get back to work on the UTF-8 support, and don't anticipate to have the time to do s

[screen-devel] [bug #55138] Bug: UTF-8 characters in hardstatus not working

2018-11-30 Thread Elof
URL: Summary: Bug: UTF-8 characters in hardstatus not working Project: GNU Screen Submitted by: elof Submitted on: Fri 30 Nov 2018 11:59:03 AM UTC Category: User Interface