Why those tools?
HTML documentation was rewritten and provide a unique menu on each page.
For a specific manual, the menu is the same, whatever the page is.

htmls.sh
--------
For each manual, the htmls.sh script is designed to achieve those steps:
a) Build and isolates the menu
b) Interpret the latex2html HTML files located into docs/manuals/en/www-{manual} and rewrite all HTML files for the manual and put them to the expected directory (docs/manuals/en/{manual}/{manual})
c) Find and note all the <a name="..."> tags into a file named list-of-anchors


translatedoc.pl
---------------
This script is called for each HTML file, read it and convert it:
- removes the specific menu
- includes the whole menu file
- add some "class=" and "<div>" ... tags
- do some comestics stuff.
- note all anchors defined into the HTML files.


handle-xr-references.pl
-----------------------
This script is designed to read the anchors found when reading original HTML files (see above)
and then replace all the __XRANCHOR_ built during the latex2html process (see docs/README.pct)
into <a href...> tag.

TODO:
-----
a) Important: Manage the language into htmls.sh. Currently only the manuals/en manuals are managed. I would suggest to pass the language value and manage it into the "SOURCEDIRHEAD" variable.

b) Cosmetic
We should add some treatments in the translatedoc.pl script to replace anchor with some more readable labels. The one generated by latex2html are way too complex in my opinion. 


index.pl
--------
This script will generate a JSON file with all \label{} references of all html files.
It is used by bweb to find the right page with a label.


index.html
----------
This page should redirect to the right documentation page, it is using js/index.js

ex: <li><a href="javascript:get_doc('6.6', 'main', 'RestoreChapter')">More...(Restore Chapter)</a></li>

