From pgcon6 at msn.com Sat Oct 11 01:59:04 2025 From: pgcon6 at msn.com (Peter Constable) Date: Sat, 11 Oct 2025 06:59:04 +0000 Subject: Changes to the Script Extension property in 16.0 that aren't documented in the release notes In-Reply-To: References: Message-ID: Hi, Karl Someone should have provided a response sooner. First, the re-ordering of data in ScriptExtensions.txt actually was done in Unicode 16.0. See https://www.unicode.org/reports/tr44/tr44-34.html#Change_History. Regarding the entry for 02C7, the script extension was changed from {Common} in 15.1 (by virtue of no entry, hence defaulting to its Script property) to {Latin, Bopomofo} in 16.0. That was part of a set of additions to ScriptExtensions.txt that UTC had approved at UTC #178 (January 2024) ? see consensus 178-C39: https://www.unicode.org/L2/L2024/24006.htm#178-C39 The change was committed into the file within the following month, and would have been visible in public review no later than the Unicode 16.0 Beta. Peter -----Original Message----- From: Unicode On Behalf Of Karl Williamson via Unicode Sent: September 14, 2025 11:37 AM To: unicode at unicode.org Subject: Changes to the Script Extension property in 16.0 that aren't documented in the release notes I got a complaint from the field that U+02C7 is unexpectedly listed as in the Latin script in 16.0 Someone investigated and the only changes listed for that property are that the ScriptExtensions.txt file has been re-ordered. I checked, and they are correct. I then looked at a difference listing between the 15.1 and 16.0 versions, and there are extensive changes beyond reordering. Is there something we're missing, or did the 16.0 changes list omit these things? -------------- next part -------------- An HTML attachment was scrubbed... URL: