[xiph-commits] r18788 - websites/opus-codec.org/license

[jm at svn.xiph.org]

Author: jm
Date: 2013-02-05 19:11:32 -0800 (Tue, 05 Feb 2013)
New Revision: 18788

Modified:
   websites/opus-codec.org/license/index.shtml.en
Log:
oops, applying previous commit to the right page


Modified: websites/opus-codec.org/license/index.shtml.en
===================================================================
--- websites/opus-codec.org/license/index.shtml.en	2013-02-06 02:24:47 UTC (rev 18787)
+++ websites/opus-codec.org/license/index.shtml.en	2013-02-06 03:11:32 UTC (rev 18788)
@@ -289,8 +289,8 @@
 
 <p>
 While Xiph.Org, Broadcom, and Microsoft filed IPR disclosures giving
- royalty-free licenses to their patents used in Opus, two companies that did
- not directly participate in the development of Opus, Qualcomm and Huawei,
+ royalty-free licenses to their patents used in Opus, three companies that did
+ not directly participate in the development of Opus, Qualcomm, Huawei, and France Telecom,
  filed IPR disclosures with potentially royalty-bearing terms.
 The IETF allows <i>anyone</i> (and their dog) to file an IPR disclosures if
  they <i>think</i> that their patents "covers or <i>may</i> ultimately cover"
@@ -312,8 +312,8 @@
 When it comes to patents, it is difficult to say much without
  making lawyers nervous.
 However, we can say something quite direct: <b>external counsel Dergosits & Noah has advised us that Opus can be
- implemented without the need to license the patents disclosed by Qualcomm or
- Huawei</b>.
+ implemented without the need to license the patents disclosed by Qualcomm,
+ Huawei, or France Telecom</b>.
 We can also say that Mozilla is confident enough in Opus to ship it to hundreds
  of millions of Firefox users.
 Similarly, Cisco and Google are also supporting Opus in some products.