Cc'ing Axel Beckert, who maintains screen. On 2023-01-03 02:28:14 +0100, Vincent Lefevre wrote: > On 2023-01-02 23:08:39 +0100, Aurelien Jarno wrote: > > This U+1FAF6 character is new in Unicode 14, which is supported starting > > with glibc 2.35. Older glibc does not know about this character, causing > > mutt to display it with '?'. With newer glibc mutt displays the > > character. > > > > Now I am not sure it is a bug in glibc, it rather seems an issue with > > screen. I can reproduce the shifts in both, stable and unstable, by > > putting this char in a file and just running cat on the file. > > I've look at the "screen" code, and it has a file encoding.c with > some kind of table (intervals) of double-width characters, and it > gives the URL of a script to regenerate these tables. > > Since these tables depend on the Unicode version (which depends on > the libc6 version), shouldn't the screen package have a versioned > dependency on libc6?
-- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
