cleanup README files.

Convert DOS -> unix newlines.
Cleanup and clarify several files.

l10ntools/README

-l10ntools is scanners module during gbuild'fication. 
-l10ntools delivers some header files and scripts as well. To 
-handle these, you should create two Packages, one for the headers and 
-other for the scripts.
-l10ntools module has three lexer files
\ No newline at end of file
+l10ntools contains a number of tools that handle internationalisation(i18n) during the build.
+

m4/README

 m4 - Macros to locate and utilise pkg-config.
+
 work around m4 bracket stripping in MINGWSTRIP construction
\ No newline at end of file

more_fonts/README

-for adding or repacing fonts
\ No newline at end of file
+This module packages some external fonts.
\ No newline at end of file

postgresql/README

 PostgreSQL object-relational database management system
+
+We use some pieces of this code for the postgresql database connector.
\ No newline at end of file

scp2/README

-java accessibilty bridge cleanup
\ No newline at end of file
+SCript Particle installer
+
+This contains code that describes which pieces of the project should
+be packaged and installed - it is used to build among other things
+a setup_osl.inf or .ins file - that is used by solenv/bin/make_installer.pl
+to build the installation.

setup_native/README

-To get one gbuild instance build only (tail_build only), migrating the "real" 
-module should be the enough for a start. I assume extras, setup_native, 
-readlicense not being depended upon by anything other than scp2 (so they could 
-be run after tail_build for now). So bridges, soltools, sysui, cli_ure are the 
-ones that should allow us to do a 'complete' gbuild-only build, if anyone is 
-looking for the 'important' remaining modules. 
\ No newline at end of file

soltools/README

-soltools: fix memory errors uncovered by valgrind and other tools.
\ No newline at end of file

stlport/README

-STLPort library for compatibility with old extensions for architectures where STLPort used to be used.
\ No newline at end of file
+The STLPort library
+
+This is used for compatibility for old extensions for architectures
+where STLPort used to be used. Noawadays we use platform native STL.
\ No newline at end of file

test/README

-when you build, gdb will start with the cppunit test loaded, type "run" to execute the test under gdb.
-If you have consistent test failures on testCVEs, that probably means your antivirus is blocking the test files (as they are known to be exploits of fixed security issues). You may want to disable the monitoring of <root of repo>\*\pass in your AV.
-A top-level "make check" will first do a full build, then run all the subsequent tests, while a top-level "make subsequentcheck" will only run all the subsequent tests. You can run a single subsequent test via its target
-There will be a log file of the failed test, you can look at it with a text editor:
-workdir/unxlngx6/JunitTest/<module>_complex/done.log
-The log file will contain a Java stack trace of the failed test
\ No newline at end of file
+Test harness code for C++ unit testing
+
+Many of these tests are run during the build process. In that case on
+unix, if a test fails follow the error messages to debug it under gdb.

unotest/README

-unotest: convert to gbuild
\ No newline at end of file