Updated README.md files to represent current code / use Markdown format

Previously, all of the README files have been renamed to README.md
and now, the contents of these files were changed to use Markdown
format. Other than format inconsistency, some README.md files lacked
information about modules, or were out of date. By using LibreOffice
/ OpenOffice wiki and other documentation websites, these files were
updated. Now every README.md file has a title, and some description.
The top-level README.md file is changed to add links to the modules.
The result of processing the Markdown format README.md files can be
seen at: https://docs.libreoffice.org/

Change-Id: Ic3b0c3c064a2498d6a435253b041df010cd7797a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/113424
Tested-by: Jenkins
Reviewed-by: Michael Stahl <michael.stahl@allotropia.de>
Reviewed-by: Adolfo Jayme Barrientos <fitojb@ubuntu.com>

1 files changed, 17 insertions, 16 deletions

diff --git a/testtools/README.md b/testtools/README.md
index c71e4c8b607d..f238c512293f 100644
--- a/testtools/README.md
+++ b/testtools/README.md
@@ -1,34 +1,35 @@
-Testing tools
+# Testing Tools
 
-== How to check compatibility between compilers ==
+## How to Check Compatibility Between Compilers
 
 Since the interfaces used in the cpp bridgetest are not changed often
-one can just build the cppobj.uno.dll and the constructors.uno.dll
-(testtools/source/bridgetest) in an
+one can just build the `cppobj.uno.dll` and the `constructors.uno.dll`
+(`testtools/source/bridgetest`) in an
 old environment and then use them in the new environment. That is the files
-are copied into the testtools/wntmsciXX.pro folder which corresponds to the
+are copied into the `testtools/wntmsciXX.pro` folder which corresponds to the
 new environment.
 
 On Windows this test will typically fail because the tests use the
-cppu::getCaughtException function, which only works when all libs are build
+`cppu::getCaughtException` function, which only works when all libs are build
 using the same runtime.
 
 This part of the test can switched off. To do this go into the
-testtools/source/bridgetest folder and call
-dmake compcheck=1
+`testtools/source/bridgetest` folder and call
 
-This will add a new compiler define (-DCOMPCHECK) and will be used in the
-bridgetest.cxx to switch off the code which uses the getCaughtException function.
+    dmake compcheck=1
+
+This will add a new compiler define (`-DCOMPCHECK`) and will be used in the
+`bridgetest.cxx` to switch off the code which uses the `getCaughtException` function.
 However, there is still a test which causes the test component to throw
-and IllegalArgumentException. This still works.
+and `IllegalArgumentException`. This still works.
 
 
-== Using source/bridgetest for stress testing ==
+## Using source / bridgetest for Stress Testing
 
-Start a modified bridgetest_server (with the final "--singleaccept" argument
-removed from the uno executable call) or a modified bridgetest_javaserver (with
-the final "singleaccept" argument replaced with "multi" in the java executable
-call), then start a modified bridgetest_client (with a final "stress" argument
+Start a modified `bridgetest_server` (with the final `--singleaccept` argument
+removed from the uno executable call) or a modified `bridgetest_javaserver` (with
+the final `singleaccept` argument replaced with `multi` in the java executable
+call), then start a modified `bridgetest_client` (with a final `stress` argument
 added to the uno executable call).  The client will continuously establish
 connections to the server which are immediately destroyed again.  The test will
 run forever, unless an error occurs.