In the OOo 2 branch, the current situation regarding license and readme files
included in product installation sets is as follows (at least on Unix, file
names may differ slightly for Windows):

- The URE (which has no locale-dependent parts other than its license and readme
files, which in turn are only available in en-US) contains
.../LICENSE
.../README
.../THIRDPARTYLICENSEREADME.html

- An Office product (e.g., plain OOo, BrOffice, StarOffice) contains
.../LICENSE
.../LICENSE.html
.../README
.../README.html
.../THIRDPARTYLICENSEREADME.html
.../licenses/LICENSE_${loc}
.../licenses/LICENSE_${loc}.html
.../readmes/README_${loc}
.../readmes/README_${loc}.html
.../share/readme/LICENSE_${loc}
.../share/readme/LICENSE_${loc}.html
.../share/readme/README_${loc}
.../share/readme/README_${loc}.html
Where all but THIRDPARTYLICENSREADME.html (which appears to always be en-US) are
potentially localized (but sometimes at least .../LICENSE[.html] is in en-US
though the rest is not), and many of the files appear to be copies of each
other.  The "${loc}" represents the locale(s) for which the product is installed.

With the new setup for the OOo 3 branch (see issue 84200), there will be three
kinds of (conceptional) products:
- URE remains a standalone product but is also reused as the lowest layer of a
three-layer Office product.
- OOo Basis is the "product" that is the common, shared basis for various Office
Brand products.  (It is the middle layer.)
- Various Brand products (the top layer).

Please clarify what kinds of license and readme files should be contained in
each kind of product.