Add and expand more readme files for module documentation

bin/README

@@ -0,0 +1,9 @@
+Tools and scripts used during the build
+
+This direction has a number of key pieces that are used during the
+build, or are simply generally useful. One example is
+
+bin/find-german-comments <directory>
+
+which will try to detect and extract all the German comments in a
+given source code hireachy / directory.

distro-configs/README

@@ -0,0 +1,14 @@
+Pre-canned distribution / platform configurations
+
+When the software is configured for a platform, since we run on so
+many platforms, detecting the best sequence of configure options to
+get it building is hard.
+
+Instead we have a text file containing the recommended (often the
+distributed) version of these parameters, one per distribution or
+significant platform. These are interpreted by autogen.sh and
+eventually end up passed to configure. Thus:
+
+./autogen.sh --with-distro=LibreOfficeAndroid
+
+might build a version tweaked for Android.

icon-themes/README

@@ -1,3 +1,24 @@
+Icon repository for the applications
+
+All of the icons, separated by themes are included in this
+directory. These icons are built into .zip files, and re-ordered /
+packed for efficiency reasons based on our UI configuration by the
+packimages/ module.
+
+An icon theme does not need to contain all images, since these can be
+layered one on top of another.
+
+In general the layering is done like this:
+
+<leaf theme>
+tango
+industrial
+galaxy
+
+The classic theme is left primarily for historical interest, rather
+than intended to be packaged.
+
+
 How to add a new image set:
 ---------------------------
 

rsc/README

@@ -1,10 +1,32 @@
 Resource Compiler.
 
-There is some German documentation about it in a subdirectory called [git:rsc/doku].
-Seems to be very old (January 1992).
+This compiler converts .src files and .hrc equivalents into binary
+.res files.  The basic idea is that this provides a map between
+integer identifiers and the resources: string, pixmap (only the
+file-name), and VCL control properties.
 
-From rsc.sdw (in German):
-The StarView Resource Compiler (rsc) is used, to convert the system-independent
-resources in the description files to native description files which in turn are
-compiled efficiently (runtime) by the system's native resource compiler in binary
-resources.
+In more detail:
+
+Typically we would have a .hrc file with entries like this:
+
+#define SID_STR_FOO    1234
+
+And then a .src file with some entries like this:
+
+String SID_STR_FOO
+{
+    Text [ en-US ] = "Foo !" ;
+};
+
+This is compiled into a binary resource file, we have many of these
+which live in program/resource/ and then tends to get used in the code
+thus:
+
+String aStr( ResId( SID_STR_FOO ) );
+
+It is important to note that any appearance of hierarchical structure
+in the .src files is in fact a mirage. The file is compiled at root
+into a plain map<integer,resource>.
+
+There is some German documentation about it in a subdirectory called
+[git:rsc/doku].  Seems to be very old (January 1992).

scaddins/README

@@ -1,4 +1,8 @@
 Extra functions for calc.
 
+These provide UNO components that implement more exotic calc
+functions. If you want to do the same, here can be a good place to
+start.
+
 See also:
 [http://wiki.services.openoffice.org/wiki/Scaddins]