Changed to the MIT Licence updated the doc accordingly preparing 2.4.14
* Copyright Makefile.am README configure.in libxml.spec.in:
Changed to the MIT Licence
* doc/FAQ.html doc/catalog.html doc/intro.html doc/xml.html
doc/xmlio.html: updated the doc accordingly
* include/libxml/xmlwin32version.h configure.in: preparing
2.4.14 release
* python/generator.py python/libxml.c python/libxml2-python-api.xml
python/libxml2class.txt python/libxml_wrap.h python/types.c:
fixed the const xmlChar * wrapper and generator, XPath extension
functions now use the context as first argument
* python/tests/tstxpath.py python/tests/xpath.py
python/tests/xpathext.py: Updated the tests accordingly
* tree.c: fixed bug #70067
Daniel
diff --git a/doc/FAQ.html b/doc/FAQ.html
index 208f7af..d41dcd0 100644
--- a/doc/FAQ.html
+++ b/doc/FAQ.html
@@ -94,18 +94,14 @@
<ol>
<li>
<em>Licensing Terms for libxml</em>
- <p>libxml is released under 2 (compatible) licences:</p>
-<ul>
-<li>the <a href="http://www.gnu.org/copyleft/lgpl.html">LGPL</a>: GNU
- Library General Public License</li>
-<li>the <a href="http://www.w3.org/Consortium/Legal/copyright-software-19980720.html">W3C
- IPR</a>: very similar to the XWindow licence</li>
-</ul>
+ <p>libxml is released under the <a href="http://www.opensource.org/licenses/mit-license.html">MIT
+ Licence</a>, see the file Copyright in the distribution for the precise
+ wording</p>
</li>
<li>
<em>Can I embed libxml in a proprietary application ?</em>
- <p>Yes. The W3C IPR allows you to also keep proprietary the changes you
- made to libxml, but it would be graceful to provide back bugfixes and
+ <p>Yes. The MIT Licence allows you to also keep proprietary the changes
+ you made to libxml, but it would be graceful to provide back bugfixes and
improvements as patches for possible incorporation in the main
development tree</p>
</li>