[HN Gopher] Unicode 15 Released
       ___________________________________________________________________
        
       Unicode 15 Released
        
       Author : asjo
       Score  : 33 points
       Date   : 2022-09-14 19:35 UTC (3 hours ago)
        
 (HTM) web link (lwn.net)
 (TXT) w3m dump (lwn.net)
        
       | teddyh wrote:
       | > _UTS #39, Unicode Security Mechanisms, changes the zero width
       | joiner (ZWJ) and zero width non-joiner (ZWNJ) characters from
       | Identifier_Status=Allowed to Identifier_Status=Restricted; they
       | are therefore no longer allowed by the General Security Profile
       | by default._
       | 
       | Good, I guess, but I wonder how much will break.
        
       | pie_flavor wrote:
       | New astrological signs!
        
       | rektide wrote:
       | Relaying some LWN comments:
       | 
       | > _Why do we get to use the "bottom left part of glyph is
       | damaged" modifier only for hieroglyphs? :(_
       | 
       | (It'd be interesting to consider modifiers not always necessarily
       | needing to be pre-encoded... to allow casual flexibility in
       | implementation)
       | 
       | Wifi and Honk are new symbols.
       | 
       | (Tiktok/instagram will be thrilled... "can I get a honkkkk". (Im
       | ok with the idea but honking is in general a nuissance that needs
       | to be shut the f down, huge anti-social problem)).
        
       | AdamH12113 wrote:
       | > _This version adds 4,489 characters, bringing the total to
       | 149,186 characters. These additions include two new scripts, for
       | a total of 161 scripts, along with 20 new emoji characters, and
       | 4,193 CJK (Chinese, Japanese, and Korean) ideographs._
       | 
       | That seems like a lot of new CJK characters! How did they end up
       | with so many new characters after so long? Is there some gradual
       | process of adding historical or extremely rare characters, or
       | were some deliberately left out of earlier versions?
        
         | ks2048 wrote:
         | On the wikipedia page for "CJK Unified Ideographs Extension H",
         | under "History"(https://en.wikipedia.org/wiki/CJK_Unified_Ideog
         | raphs_Extensi...), you can find dozens of linked documents
         | describing why someone thought they should be added.
         | 
         | One random example I opened
         | (https://www.unicode.org/L2/L2017/17099-haifeng-county-
         | uax45....) is a 9 page PDF proposing a single character used
         | for "congee shop signs in Haifeng County".
        
         | lifthrasiir wrote:
         | More like the former. There was indeed a deliberate omission in
         | the past standard called Han unification [1], but it's now
         | pretty much toned down thanks to the expansion of Unicode
         | codepoint space in 2.0, following subsequent disunification
         | processes and the eventual introduction of Ideographic
         | Variation Database [2] to handle remaining cases.
         | 
         | [1] https://en.wikipedia.org/wiki/Han_unification
         | 
         | [2] https://unicode.org/ivd/
        
       | pacaro wrote:
       | https://blog.unicode.org/2022/09/announcing-unicode-standard...
       | 
       | Seems like it might be a better link
        
         | gmfawcett wrote:
         | > Unicode is required by modern standards such as XML, Java,
         | C#, ECMAScript (JavaScript), LDAP, CORBA 3.0, WML, etc.,
         | 
         | TIL that CORBA is still around, and that someone considers it
         | modern.
        
           | rektide wrote:
           | Repeating my general request, someone please do a Speaking
           | for the Dead on COBRA that includes the good, the hopeful,
           | the smart.
           | 
           | Also the bad too. These days it's just a sign a symbol for
           | bad, but in this hyperreity we dont know the referrant, dont
           | know the lessons of the bad either.
           | 
           | But i want to hear the good most of all. And how good was
           | avoided. Because it I think like so much else might possibly
           | have gone great, if things & times & adoption had been only
           | slightly barely different. It was just too soon for open
           | source, is a huge possibility in my mind.
           | 
           | Also comparison versus DCOM/OLE would be informative, for
           | historical context.
        
       ___________________________________________________________________
       (page generated 2022-09-14 23:01 UTC)