Re: [screen-devel] suspicious code in encoding.c

2022-02-22 Thread Carl Drougge
On Fri, Feb 18, 2022 at 02:15:05 +0100, Vincent Lefevre wrote: > Indeed, the code is really strange: > > (c & 0x300) >> 12 ^ 0xf8 > > will be stored in a char. So why dealing with bits more significant > than the 8 bits of a char? I too recently noticed this. I have now made a nice clean

[screen-devel] [bug #62097] UTF-8 should be limited to valid range

2022-02-22 Thread Carl Drougge
Follow-up Comment #1, bug #62097 (project screen): Sorry, I should have actually tried the V5 patch and noticed the compiler warning (harmless though it is). Fixed patch attached. (file #52906) ___ Additional Item Attachment: File name: 00

[screen-devel] [bug #62097] UTF-8 should be limited to valid range

2022-02-22 Thread Carl Drougge
URL: Summary: UTF-8 should be limited to valid range Project: GNU Screen Submitted by: drougge Submitted on: Tue 22 Feb 2022 07:24:08 PM UTC Category: Program Logic Se