RE: Klingon tagging (was: RE: Seeming hostility to conlang scripts?)
Phil Smith III via Unicode <[email protected]> Sun, 14 Jun 2026 07:30:48 -0400
| Newsgroups | gmane.text.unicode.general |
|---|---|
| Message-ID | <[email protected]> |
This is a multipart message in MIME format. ------=_NextPart_000_0022_01DCFBCF.B9024CD0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable From my casual reading of this thread, it sounds to me like the = Consortium is trying to avoid cases where they=E2=80=99re actively = concerned about such copyright trolling. Your point makes sense, but = falls into the =E2=80=9CWe hope nobody does that; if they do, = we=E2=80=99ll have to address this, which will take years and cost = millions of lives=E2=80=9D (well, dollars). In the meantime, = they=E2=80=99re avoiding poking the obvious bears. Almost a = =E2=80=9CDon=E2=80=99t ask, don=E2=80=99t tell=E2=80=9D kind of = thing=E2=80=A6 =20 So =E2=80=9CThere's *gotta* be a limit=E2=80=9D is true=E2=80=94but the = Consortium doesn=E2=80=99t want to spend their money finding out where = that is if they don=E2=80=99t have to. Which, alas, makes sense in this = crazy, litigious environment. =20 From: Unicode <[email protected]> On Behalf Of Vikki = McDonough via Unicode Sent: Saturday, June 13, 2026 4:02 PM To: Piotr Karocki <[email protected]> Cc: [email protected] Subject: Re: Klingon tagging (was: RE: Seeming hostility to conlang = scripts?) =20 There's *gotta* be a limit to how badly copyright trolls (I use this = term because it seems clear to me that a script, being a = purely-*functional* device, falls outside the gamut of productions in = the "literary, scientific, and artistic domain" that're copyrightable = under the Berne Convention) can kneecap Unicode's ability to encode = things, though, right? Otherwise, any country in the world could decree = that it provides an infinite-length copyright term for both domestic and = foreign works, and thereby completely destroy Unicode's ability to = encode any scripts not already encoded. =20 On Sat, Jun 13, 2026, 1:45=E2=80=AFPM Piotr Karocki via Unicode = <[email protected] <mailto:[email protected]> > wrote: > In any event, there is a difference between recognizing that something = is > a script > from an ISO 15924 standpoint and determining that it meets Unicode > encoding standards. Ok, but if klingon is officially recognized as script, the only argument = to not include it in Unicode can be based on "we cannot include copyrighted glyphs". Argument "it is not used" is invalidated. =20 =20 - Vikki McDonough =F0=9F=8F=B3=EF=B8=8F=E2=80=8D=E2=9A=A7=EF=B8=8F ------=_NextPart_000_0022_01DCFBCF.B9024CD0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" = xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta = http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta = name=3DGenerator content=3D"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:Aptos;} @font-face {font-family:"Segoe UI Emoji"; panose-1:2 11 5 2 4 2 4 2 2 3;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; font-size:12.0pt; font-family:"Aptos",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} span.EmailStyle18 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:#0A2F41;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt; mso-ligatures:none;} @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=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue = vlink=3Dpurple style=3D'word-wrap:break-word'><div = class=3DWordSection1><p class=3DMsoNormal><span = style=3D'font-family:"Calibri",sans-serif;color:#0A2F41'>From my casual = reading of this thread, it sounds to me like the Consortium is trying to = avoid cases where they=E2=80=99re actively concerned about such = copyright trolling. Your point makes sense, but falls into the = =E2=80=9CWe hope nobody does that; if they do, we=E2=80=99ll have to = address this, which will take years and cost millions of lives=E2=80=9D = (well, dollars). In the meantime, they=E2=80=99re avoiding poking the = obvious bears. Almost a =E2=80=9CDon=E2=80=99t ask, don=E2=80=99t = tell=E2=80=9D kind of thing=E2=80=A6<o:p></o:p></span></p><p = class=3DMsoNormal><span = style=3D'font-family:"Calibri",sans-serif;color:#0A2F41'><o:p> </o:p= ></span></p><p class=3DMsoNormal><span = style=3D'font-family:"Calibri",sans-serif;color:#0A2F41'>So = =E2=80=9C</span>There's *gotta* be a limit<span = style=3D'font-family:"Calibri",sans-serif;color:#0A2F41'>=E2=80=9D is = true=E2=80=94but the Consortium doesn=E2=80=99t want to spend their = money finding out where that is if they don=E2=80=99t have to. Which, = alas, makes sense in this crazy, litigious = environment.<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'font-family:"Calibri",sans-serif;color:#0A2F41'><o:p> </o:p= ></span></p><div style=3D'border:none;border-top:solid #E1E1E1 = 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span><= /b><span style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif'> = Unicode <[email protected]> <b>On Behalf Of = </b>Vikki McDonough via Unicode<br><b>Sent:</b> Saturday, June 13, 2026 = 4:02 PM<br><b>To:</b> Piotr Karocki <[email protected]><br><b>Cc:</b> = [email protected]<br><b>Subject:</b> Re: Klingon tagging (was: = RE: Seeming hostility to conlang scripts?)<o:p></o:p></span></p></div><p = class=3DMsoNormal><o:p> </o:p></p><div><div><div><p = class=3DMsoNormal>There's *gotta* be a limit to how badly copyright = trolls (I use this term because it seems clear to me that a script, = being a purely-*functional* device, falls outside the gamut of = productions in the "literary, scientific, and artistic domain" = that're copyrightable under the Berne Convention) can kneecap Unicode's = ability to encode things, though, right? Otherwise, any country in = the world could decree that it provides an infinite-length copyright = term for both domestic and foreign works, and thereby completely destroy = Unicode's ability to encode any scripts not already = encoded.<o:p></o:p></p></div></div><p = class=3DMsoNormal><o:p> </o:p></p><div><div><p class=3DMsoNormal>On = Sat, Jun 13, 2026, 1:45<span = style=3D'font-family:"Arial",sans-serif'>=E2=80=AF</span>PM Piotr = Karocki via Unicode <<a href=3D"mailto:[email protected]" = target=3D"_blank">[email protected]</a>> = wrote:<o:p></o:p></p></div><blockquote = style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in = 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5= .0pt'><p class=3DMsoNormal>> In any event, there is a difference = between recognizing that something is<br>> a script<br>> from an = ISO 15924 standpoint and determining that it meets Unicode<br>> = encoding standards.<br><br>Ok, but if klingon is officially recognized = as script, the only argument to<br>not include it in Unicode can be = based on "we cannot include copyrighted<br>glyphs". Argument = "it is not used" is = invalidated.<o:p></o:p></p></blockquote></div><p class=3DMsoNormal = style=3D'margin-bottom:12.0pt'><o:p> </o:p></p><div><div><div><p = class=3DMsoNormal><o:p> </o:p></p></div><p class=3DMsoNormal>- = Vikki McDonough <span style=3D'font-family:"Segoe UI = Emoji",sans-serif'>🏳=EF=B8=8F=E2=80=8D=E2=9A=A7=EF=B8=8F</span><o= :p></o:p></p></div></div></div></div></body></html> ------=_NextPart_000_0022_01DCFBCF.B9024CD0--