<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 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#002060;}
.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='color:#002060'>Whether or not foundrys will produce fonts seems like a commercial question separate from whether a script should be encoded. Certainly some of the scripts in Unicode have very bare font support. Is there a criteria in Unicode that says only encode a script if at least this many fonts will be produced? Not that I am aware of. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#002060'>In any event, since Klingon fonts are already available, the questions are moot.<o:p></o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span style='color:#002060'><o:p> </o:p></span></a></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Unicode [mailto:unicode-bounces@corp.unicode.org] <b>On Behalf Of </b>Peter Constable via Unicode<br><b>Sent:</b> Saturday, September 18, 2021 5:26 PM<br><b>To:</b> Ken Whistler; Mark E. Shoulson; unicode@unicode.org<br><b>Subject:</b> RE: Difference between Klingon and Tengwar<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><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><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Peter<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> Unicode <unicode-bounces@corp.unicode.org> <b>On Behalf Of </b>Ken Whistler via Unicode<br><b>Sent:</b> September 17, 2021 8:24 AM<br><b>To:</b> Mark E. Shoulson <mark@kli.org><br><b>Cc:</b> unicode@corp.unicode.org<br><b>Subject:</b> Re: Difference between Klingon and Tengwar<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p>Mark,<o:p></o:p></p><p>By _users_ here, Peter doesn't mean some random end user using their communicator (err, smart phone) to send piQaD messages at a StarTrek fan convention, but rather the implementing companies who put piQaD keyboards and fonts on those smart phones. If somebody wakes up at Paramount and wonders, hmmm, does Apple (or Google, or Samsung, or ...) have a license from us for that Klingon stuff they just put on their phones, those are far juicier targets for an IP infringement lawsuit, *even if* the likeliest outcome would not be a decisive win in a court case, but rather just some out of court settlement. Even an out of court settlement in some case like this would set a terrible precedent, encouraging other people claiming IP rights on some writing system being considered for encoding in the Unicode Standard.<o:p></o:p></p><p>--Ken<o:p></o:p></p><div><p class=MsoNormal>On 9/16/2021 6:17 PM, Mark E. Shoulson via Unicode wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p>Now, Peter Constable writes:<o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>The main concern is that _<i>users</i>_ of The Unicode Standard won’t be susceptible to IP claims against them. Since this is uncertain, the onus is on the advocates for encoding the script to resolve that.<o:p></o:p></p></blockquote><p>which is an angle I actually had not heard before. And here I'm really puzzled. The users of the script are already using the script, whether Unicode encodes it or not. So why is Unicode suddenly concerned on their behalf? This one is really kind of strange. Could Unicode be legally responsible for people "illegally" using the script? It's hardly in Unicode's power to stop them, as evidence by the fact that usage exists.<o:p></o:p></p></blockquote></div></body></html>