Difference between Klingon and Tengwar

[Peter Constable]

The main concern is that _users_ 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.


Peter


From: Unicode <unicode-bounces at corp.unicode.org> On Behalf Of William_J_G Overington via Unicode
Sent: September 16, 2021 3:07 AM
To: unicode at corp.unicode.org
Subject: Re: Difference between Klingon and Tengwar

What exactly, precisely would Unicode Inc. need in relation to the Intellectual Property Rights in order to proceed please?



Would a permanent licence to use the glyph designs in The Unicode Standard be enough?



Would Unicode Inc. be willing to pay the owner of the Intellectual Property Rights a one-off payment of one United States Dollar as consideration for providing such a licence if that were the way to resolve the matter satisfactorily?



Would Unicode Inc. be willing to include in The Unicode Standard and in the code chart a statement mentioning the licence and thanking the owner of the Intellectual Property Rights?



William Overington



Thursday 16 September 2021






------ Original Message ------
From: "William_J_G Overington via Unicode" <unicode at corp.unicode.org<mailto:unicode at corp.unicode.org>>
To: unicode at corp.unicode.org<mailto:unicode at corp.unicode.org>
Sent: Thursday, 2021 Sep 16 At 00:39
Subject: Re: Difference between Klingon and Tengwar
Mark Davis wrote:

> And those are still a barrier: there is no point in even starting to consider the Klingon script unless and until the IP problem is completely resolved.



Yet if Unicode Inc. were to do most of the necessary work first and then write to the Intellectual Property Rights owners stating that Unicode Inc. would like to encode the Klingon glyphs into Unicode, and would do so if the Intellectual Property Rights issues could be resolved, and including a detailed draft of what this encoding would involve, then maybe that would lead to progress.



William


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://corp.unicode.org/pipermail/unicode/attachments/20210916/d0f41d62/attachment.htm>