<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Bierstadt;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.E-MailFormatvorlage21
{mso-style-type:personal-compose;
font-family:"Bierstadt",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Bierstadt",sans-serif">Note that Microsoft provided a pIqaD version of the Bing translator as part of the Klingon translation, using the PUA conscript codepoints. It was ‘my’ font, though it was also available
for free. It was up for years, though as developers working on it moved it isn’t currently up. But Microsoft had an agreement
</span><span style="font-family:"Segoe UI Emoji",sans-serif">😊</span><span style="font-family:"Bierstadt",sans-serif"> (I know there are translation quality issues, that’s out of my control).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bierstadt",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bierstadt",sans-serif">There was a brief conversation of the encoding at that time, but, like Mark’s efforts, it didn’t really get to the right people to sign off.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bierstadt",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bierstadt",sans-serif">I do think that Mark makes some good points about the current language of the rejection perhaps being a bit off-putting for any future discussions should someone be able to contact the right
person at Paramount. IMO, perhaps it would be good to formally propose it again, and get a rejection that explicitly notes the primary concern is around the IP. And hopefully doesn’t otherwise impugn the worthiness of the proposal.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bierstadt",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bierstadt",sans-serif">-Shawn<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bierstadt",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bierstadt",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="DE">Von:</span></b><span lang="DE"> Unicode <unicode-bounces@corp.unicode.org>
<b>Im Auftrag von </b>Mark E. Shoulson via Unicode<br>
<b>Gesendet:</b> Sunday, September 19, 2021 4:41 PM<br>
<b>An:</b> unicode@corp.unicode.org<br>
<b>Betreff:</b> Re: Difference between Klingon and Tengwar<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 9/18/21 8:25 PM, Peter Constable via Unicode wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Indeed.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Consider some professional but small type foundry. Are they going to want to create fonts and sell licenses when there’s a question as to whether Paramount might go after them?<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Consider a large software / device vendor: will their legal departments sign off on supporting the script?<o:p></o:p></p>
</blockquote>
<p>These would seem to be their decisions, not yours. Type foundries rip off one another's designs all the time in all sorts of scripts, but that doesn't affect encodability. Moreover, I point out again that it's *already being done* by people who are apparently
willing to take the risk even before Unicode encodes things. They'll probably carry on doing so afterward as well. If nobody else does, well, that's for the invisible hand of capitalism to influence.<o:p></o:p></p>
<p>~mark<o:p></o:p></p>
</div>
</body>
</html>