Added and improved READMEs for modules in libs-extern-sys

berkeleydb/README

+The Berkeley database.

boost/README

+From [http://www.boost.org/].
+
+Apart from the spirit parsing framework, LibreOffice currently mostly
+uses the smart pointers, pool memory and binders functionality.

cairo/README

+The graphics library, used for anti-aliasing. From [http://cairographics.org/].

curl/README

+A URL manipulation engine from [http://curl.haxx.se/].

expat/README

+Simple SAX parser library with added UCS2 support.
+
+From:
+[http://expat.sourceforge.net/]

graphite/README

+Library for providing rendering capabilities for complex non-Roman writing systems.
+
+From:
+[http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&cat_id=RenderingGraphite]

hunspell/README

+Library for spell checking.
+
+From:
+[http://hunspell.sourceforge.net/].

icu/README

+Library providing Unicode support, from [http://site.icu-project.org/].
+
+== Makefiles ==
+The procedure of creating and maintaining makefiles.zip
+
+The automatically generated makefiles are not necessarily optimal.
+The build is started from allinone/all directory, and the all.mak file is used
+to build the entire module through. Each subtarget in this file is going to be
+made recursively unless there is a switch RECURSE=0. If the switch is available,
+for each subtarget all its prerequisites should be made earlier than the subtarget itself.
+Therefore, you should order the ALL target's prerequisites so that they are going
+to be built in a consistent order. Unfortunately there's no automatic process for it,
+just prove the prerequisites for each subtarget and push them forward in target's ALL
+prerequisites list. The changes between generated & optimized all.mak can be seen when
+comparing the files from v1.5 & v1.6 of makefiles.zip.

icu/Readme

-This file describes the procedure of creating and maintaining makefiles.zip
-# Obo's part
-
-    The automatically generated makefiles are not necessarily optimal. The build is started from allinone/all directory, and the all.mak file is used to build the entire module through. Each subtarget in this file is going to be made recursively unless there is a switch RECURSE=0. If the switch is available, for each subtarget all its prerequisites should be made earlier than the subtarget itself. Therefore, you should order the ALL target's prerequisites so that they are going to be built in a consistent order. Unfortunately there's no automatic process for it, just prove the prerequisites for each subtarget and push them forward in target's ALL prerequisites list. The changes between generated & optimized all.mak can be seen when comparing the files from v1.5 & v1.6 of makefiles.zip.

jpeg/README

+Support for jpeg-format. (Which library, where used ???)

libxml2/README

+Gnome xml parser library written in C, from [http://xmlsoft.org/]

libxslt/README

+Gnome xslt library written in C, from [http://xmlsoft.org/xslt/]

moz/README

-Used for security features, if nss is not available.
-
-Rebuild moz whenever changes have been made in the nss module. Those libs are
-merged into mozruntime.zip which is build in this project.
-
-Please read, please read about [[nss]].
\ No newline at end of file
+Used for security features, if nss is not available.
+
+Rebuild moz whenever changes have been made in the nss module. Those libs are
+merged into mozruntime.zip which is build in this project.
+
+Please read, please read about [[nss]].

neon/README

+Web library to help deal with WebDAV or other protocols, from [http://www.webdav.org/neon/].

nss/readme.txt → nss/README

-Relation between nss, moz, moz_prebuilt
----------------------------------------
+Containes the security libraries which are also part of [[moz]]. However nss is meant to be more current.
+
+== Relation between nss, moz, moz_prebuilt ==
+
 nss containes the security libraries which are also part of moz. However nss is
 meant to be more current, that is it to be updated more often. This should be
-easier than doing this with moz. 
+easier than doing this with moz.
 
 If nss is build depends on an environment variable (SYSTEM_NSS=NO) which
 is per default set to YES. In this case nss is build before moz. The nss
@@ -20,23 +22,24 @@ Also when moz was updated to use a newer version of mozilla, then one must make
 sure that new files which also belong to nss are not delivered and are removed
 from mozruntime.zip.
 
-Fips 140 and signed libraries
--------------------------------
+
+== Fips 140 and signed libraries ==
+
 Fips 140 mode is not supported. That is, the *.chk files containing the
 checksums for the cryptographic module are not delivered into solver and will
 not be part of the OOo installation sets.
 
-Signing has been turned off because 
+Signing has been turned off because
 - we change the rpath (install names)  after signing which breaks the signatures
 (Mac)
 - sqlite conflicts with the system sqlite when signing which breaks the build
 
 
-libfreebl3
-----------
+== libfreebl3 ==
+
 Porting to other platforms may require to deliver other variants of
 libfreebl*. The library name varies according to the platform. Changes need to
-be made to 
+be made to
 ooo/moz/extractfiles.mk
 ooo/moz/zipped/makefile.mk
 sun/moz_prebuilt/zipped/makefile.mk
@@ -45,8 +48,8 @@ See also
 http://www.mozilla.org/projects/security/pki/nss/tech-notes/tn6.html
 
 
-Windows builds of nss
----------------------
+== Windows builds of nss ==
+
 To build mozilla on windows you'll need the mozilla build tools
 
 Build requirements containing the link to the build tools:
@@ -56,13 +59,14 @@ The direct link:
 
 http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-1.3.exe
 
-libsqlite3
-----------
+
+== libsqlite3 ==
+
 The problem described here was found on Mac with OS 10.6
 NSS cannot use the system sqlite on Mac because the base line is still MacOS
 10.4. That system sqlite is incompatible with the softokn3 in nss which requires
-a later version of sqlite. 
-When we used a more current Mac SDK then we could set 
+a later version of sqlite.
+When we used a more current Mac SDK then we could set
 NSS_USE_SYSTEM_SQLITE=1
 to build using the system sqlite.
 
@@ -71,5 +75,5 @@ used by tools of the build environment. Using the sqlite from NSS breaks the
 tools if they use system libraries which are linked with the system
 sqlite. Therefore we deliver it into lib/sqlite on unix systems.
 
-See also issue 
+See also issue
 http://qa.openoffice.org/issues/show_bug.cgi?id=106132

python/README

+Python interpreter from [http://www.python.org/]

saxon/README

+XSLT and XQuery Processor from [[http://saxon.sourceforge.net/]]

stax/README

+Library implementing the Streaming API for XML. (CH: Which one, probably the one by Sun???)

zlib/README

+Compression library from [http://www.zlib.net/].