Nothing in the proposal has “interesting” (aka complex) encoding or presentation rules. I didn’t see any presentation rule changes at all, and all the encodings are straightforward. It has a lot of text dedicated to how they picked which numbers represent what glyph, and why they decided to pick some glyphs to represent and others to leave out of Unicode (at this time).
It is basically “here are a few thousand glyphs with names and example illustrations that we want”, none of the complex “this is how the letter form changes when found near this other sequence” that all the “shortish string that can crash an iPhone” exploits have used.
That’s no promise that there isn’t something in there, or that it won’t somehow interact with existing complexity in some weird way…
…but I think this is less a threat to my iphone’s Uptime, and more a threat to the legibility of my personal Swift code.
