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

[jm at svn.xiph.org]

Author: jm
Date: 2013-02-05 18:24:47 -0800 (Tue, 05 Feb 2013)
New Revision: 18787

Modified:
   websites/opus-codec.org/license/other_disclosures.shtml.en
Log:
Add France Telecom to "other disclosures"


Modified: websites/opus-codec.org/license/other_disclosures.shtml.en
===================================================================
--- websites/opus-codec.org/license/other_disclosures.shtml.en	2013-01-29 09:48:05 UTC (rev 18786)
+++ websites/opus-codec.org/license/other_disclosures.shtml.en	2013-02-06 02:24:47 UTC (rev 18787)
@@ -5,8 +5,9 @@
 
 <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 <b>anyone</b> (and their dog) to file an IPR disclosures if
  they <b>think</b> that their patents "covers or <b>may</b> ultimately cover"
@@ -28,11 +29,11 @@
 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 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 is also supporting Opus in at least one product.
+Similarly, Google now supports Opus in Chrome and Cisco also supports Opus in at least one product.
 More companies are expected to do the same soon.
 </p>