<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">As I understand it, the encoded repertoire for Sutton SignWriting is inadequate for actual display of text because Unicode doesn’t provide a mechanism for the two-dimensional layout SignWriting uses (TUS p. 831). In this, it’s like music and mathematics. <br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Nov 3, 2021, at 5:22 PM, abrahamgross--- via Unicode <<a href="mailto:unicode@corp.unicode.org" class="">unicode@corp.unicode.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<div class=""> <span dir="ltr" style="font-family:sans-serif;margin-top:0; margin-bottom:0" class="">Sutton Signwriting is completely compositional, and yet it was encoded despite all the downfalls</span>
<br class="">
<div class="">
<br class="">
<div class=""><p class="">2021/11/03 午後6:19:32 john_h_jenkins via Unicode <<a href="mailto:unicode@corp.unicode.org" class="">unicode@corp.unicode.org</a>>:</p>
</div>
<blockquote style="border-left:3px solid #ccc; padding-left:3px" class="">
<div class=""> <span class=""></span>
<br class=""><span class="">This is actually touched on in TUS (§ 18.2) and the FAQ (Why doesn't the Unicode Standard adopt a compositional model for encoding Han ideographs? Wouldn't that save a large number of code points?). Outside of the momentum issue mentioned, compositional methods don’t work because of “spelling” ambiguity and failure to address issues such as collation, text-to-speech, searching, semantic analysis—basically, everything you want to use text for *other* than rendering. Even in rendering, you aren’t covering the region-specific shapes, at least not with IDS.</span>
<br class="">
</div>
</blockquote>
</div>
</div>
</div></blockquote></div><br class=""></body></html>