diff options
author | jmvalin <jmvalin@0101bb08-14d6-0310-b084-bc0e0c8e3800> | 2002-07-01 12:05:52 +0400 |
---|---|---|
committer | jmvalin <jmvalin@0101bb08-14d6-0310-b084-bc0e0c8e3800> | 2002-07-01 12:05:52 +0400 |
commit | 7aa62d5a593ca38fb0011301089e16df258cb2f3 (patch) | |
tree | 70c880a898af5135f0462b59a254f4f56896aec6 /html | |
parent | 308726f37879fa49087fd7f19d8860f1a3b96f3a (diff) |
..
git-svn-id: http://svn.xiph.org/trunk/speex@3460 0101bb08-14d6-0310-b084-bc0e0c8e3800
Diffstat (limited to 'html')
-rw-r--r-- | html/patents.html | 46 |
1 files changed, 26 insertions, 20 deletions
diff --git a/html/patents.html b/html/patents.html index 96ffcc1..07f5537 100644 --- a/html/patents.html +++ b/html/patents.html @@ -2,32 +2,38 @@ <html> <head> <title>Speex and patents</title> + <meta name="author" content="Jean-Marc Valin"> </head> -<body> -<div align="center"> + <body> + +<div align="center"> <h1>Position regarding patents</h1> -<div align="left">Although Speex tries to avoid using patented algorithms, -we cannot provide any warranty that Speex is indeed completely patent-free. -This is because the whole field of speech coding is a real patent minefield, -with the scope of many patent still unclear. Also, each country has its own -patent laws and list of granted patents so tracking them all would be next -to impossible.<br> + +<div align="left">The goal of Speex is to provide a codec that is open-source +(released under the <a href="http://www.gnu.org/licenses/lgpl.html">LGPL</a>) +and that can be used in open-source software. This implies that it also has +to be free from patent restrictions. Unfortunately, the field of speech coding +known to be a real patent minefield and to make the matter worse, each country +has its own patent laws and list of granted patents so tracking them all +would be next to impossible. This is why we cannot provide an absolute warranty +that Speex is indeed completely patent-free.<br> <br> -That being said, we are doing our best to keep away from known patents and -we do not patent the algorithms we use. That's about all we can do about -it. If you are aware of a patent issue with Speex, please <a + That being said, we are doing our best to keep away from known patents and +we do not patent the algorithms we use. That's about all we can do about it. +If you are aware of a patent issue with Speex, please <a href="mailto:speex-devel@lists.sourceforge.net">let us know</a>.<br> -<br> -For the reasons explained above, we strongly suggest that you have a closer -look at patent issues with respect to your country if you are thinking about -using Speex commercially. Note that this is not specific to Speex, since -many "standard" codecs have an unclear patent status (like <a + <br> +Normally there shouldn't be any problem when you use Speex. However for the +reasons explained above, if you are thinking about using Speex commercially, +we strongly suggest that you have a closer look at patent issues with respect +to your country. Note that this is not specific to Speex, since many "standardized" +codecs have an unclear patent status (like <a href="http://www.mp3-tech.org/patents.html">MP3</a>, <a - href="http://kbs.cs.tu-berlin.de/%7Ejutta/toast.html">GSM</a> and probably -others), not to mention the risks of a patent holder claiming rights on a -standardized codec long after standardization.<br> -</div> + href="http://kbs.cs.tu-berlin.de/%7Ejutta/toast.html">GSM</a> and probably +others), not to mention the risks of a previously unknown patent holder claiming +rights on a standardized codec long after standardization.<br> </div> + </div> </body> </html> |