This is the mail archive of the libc-locales@sourceware.org mailing list for the GNU libc locales project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug localedata/21828] 2.26 changelog should mention user visible changes with unicode 9.0


https://sourceware.org/bugzilla/show_bug.cgi?id=21828

--- Comment #3 from Mike FABIAN <maiku.fabian at gmail dot com> ---
(In reply to dx from comment #0)
> Hi. The current version of the NEWS file for glibc 2.26 says:
> 
> >* Unicode 10.0.0 Support: Character encoding, character type info, and
> >  transliteration tables are all updated to Unicode 10.0.0, using
> >  generator scripts contributed by Mike FABIAN (Red Hat).
> 
> Previous versions also said "These updates cause user visible changes". 2.25
> was unicode 8.0, and unicode 9.0 made one very visible change in the east
> asian width[1][2] tables:
> 
> >Changed ED4 in Section 4 to state that characters with UTR #51 property
> >Emoji_Presentation to be East Asian Wide
> 
> In other words, wcwidth(U+1F355) was 1 and is now 2, same thing for other
> emoji. 

Yes, and this does indeed effect the rendering a lot when pango is used, see:

https://bugzilla.gnome.org/show_bug.cgi?id=780669#c5

Fixes in pango are required to make emoji sequences render correctly again
which were broken because of the wcwidth changes.

> Aside from being directly user visible (affecting UI rendering), this could
> also result in glitches in remotely accessed terminal applications that
> depend on this value matching between the server and the client's terminal.
> Same thing that happened with the unicode 7.0 update, and not glibc's fault
> of course.
> 
> Usually it's nothing big, some terminal box drawing alignment issues, but
> sometimes the desync results in partial redraws and leaving garbage on
> screen, or replacing some characters with others. I've been meaning to
> figure out a way to make it less ugly in that last instance, but it doesn't
> seem like it will happen before glibc 2.26 is out.
> 
> So yeah, mentioning that it's a user visible change would be helpful.
> 
> Thanks.
> 
> [1] http://www.unicode.org/reports/tr11/
> [2] http://www.unicode.org/reports/tr11/tr11-31.html#Modifications

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]