<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Yes, OTL GSUB has a one-to-many lookup
type (GSUB lookup type 2), but I don’t think this is relevant to
the issue of emoji in text-to-speech systems.</div>
<div class="moz-cite-prefix"><br>
</div>
<blockquote type="cite"
cite="mid:59970de0.1fa49.1853f741ab2.Webtop.96@btinternet.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="auto-created-dir-div" dir="auto" style="unicode-bidi:
embed;">
<div style=""><span style="display: inline !important;">I am
wondering if a font could have a table where the codepoint
(or postscript name) of an emoji is substituted by the
codepoints of a sequence of regular text characters, with
the output then routed to a text to speech system.</span></div>
</div>
</blockquote>
<p>GSUB operates at the glyph ID number level, not at the codepoint
level. Text-to-speech and text-to-glyphs can be seen as parallel
but separate presentation technologies, both sitting on top of
Unicode encoded text, but presenting that text in different ways.
Text-to-speech systems rely on natural language processing, and
the reason they become clunky when dealing with emoji—as with
other symbols and non-linguistic content—is that such characters
do not participate in linguistic communication, so at best have to
be named or described. But what is being named or described is
still at the character level, not at the glyph level.<br>
</p>
<p>JH<br>
</p>
<pre class="moz-signature" cols="72">--
John Hudson
Tiro Typeworks Ltd <a class="moz-txt-link-abbreviated" href="http://www.tiro.com">www.tiro.com</a>
Tiro Typeworks is physically located on islands
in the Salish Sea, on the traditional territory
of the Snuneymuxw and Penelakut First Nations.
__________
EMAIL HOUR
In the interests of productivity, I am only dealing
with email towards the end of the day, typically
between 4PM and 5PM. If you need to contact me more
urgently, please use other means.</pre>
</body>
</html>