#107931# synch with OOO_STABLE_1

1 files changed, 31 insertions, 31 deletions

diff --git a/odk/docs/tools.html b/odk/docs/tools.html
index 188d74cb1d0d..a5b946cad111 100644
--- a/odk/docs/tools.html
+++ b/odk/docs/tools.html
@@ -51,7 +51,7 @@
       <table width="100%" border="0" cellpadding="4">
         <tr>
           <td colspan="4" align=center><a name="tools"/><font size="6"><b>Development Tools</b></font>
-	    &nbsp;&nbsp;<a href="../index.html">SDK home</a>
+	    &nbsp;&nbsp;<a href="../index.html" title="link to the SDK start page">SDK home</a>
 	  </td>
         </tr>
         <tr> 
@@ -60,7 +60,7 @@
         <tr>
 	  <td width=2%></td>
           <td width=10%>
-             <font size="3"><a href="#idlc">idlc</a></font>
+             <font size="3"><a href="#idlc" title="link to the idlc tool description">idlc</a></font>
           </td>
           <td width=86%>
             The UNOIDL compiler, generates a common binary type library format as base for all codemaker 
@@ -71,7 +71,7 @@
         <tr>
 	  <td width=2%></td>
           <td width=10%>
-             <font size="3"><a href="#cppumaker">cppumaker</a></font>
+             <font size="3"><a href="#cppumaker" title="link to the cppumaker tool description">cppumaker</a></font>
           </td>
           <td width=86%>
             Tool for generating C++ code for the UNOIDL types stored in a type library.
@@ -81,7 +81,7 @@
         <tr>
 	  <td width=2%></td>
           <td width=10%>
-             <font size="3"><a href="#javamaker">javamaker</a></font>
+             <font size="3"><a href="#javamaker" title="link to the javamaker tool description">javamaker</a></font>
           </td>
           <td width=86%>
             Tool for generating Java code for the UNOIDL types stored in a type library.
@@ -91,7 +91,7 @@
         <tr>
 	  <td width=2%></td>
           <td width=10%>
-             <font size="3"><a href="#rdbmaker">rdbmaker</a></font>
+             <font size="3"><a href="#rdbmaker"  title="link to the rdbmaker tool description">rdbmaker</a></font>
           </td>
           <td width=86%>
             Tool for building type libraries with only a specified set of types and their dependencies.
@@ -101,7 +101,7 @@
         <tr>
 	  <td width=2%></td>
           <td width=10%>
-             <font size="3"><a href="#pkgchk">pkgchk</a></font>
+             <font size="3"><a href="#pkgchk"  title="link to the pkgchk tool description">pkgchk</a></font>
           </td>
           <td width=86%>
             The UNO package deployment tool.
@@ -111,7 +111,7 @@
         <tr>
 	  <td width=2%></td>
           <td width=10%>
-             <font size="3"><a href="#regcomp">regcomp</a></font>
+             <font size="3"><a href="#regcomp"  title="link to the regcomp tool description">regcomp</a></font>
           </td>
           <td width=86%>
             The UNO component registration tool.
@@ -121,7 +121,7 @@
         <tr>
 	  <td width=2%></td>
           <td width=10%>
-             <font size="3"><a href="#regmerge">regmerge</a></font>
+             <font size="3"><a href="#regmerge"  title="link to the regmerge tool description">regmerge</a></font>
           </td>
           <td width=86%>
             Tool to merge several registry (type libraries) files into one file.
@@ -131,7 +131,7 @@
         <tr>
 	  <td width=2%></td>
           <td width=10%>
-             <font size="3"><a href="#regview">regview</a></font>
+             <font size="3"><a href="#regview"  title="link to the regview tool description">regview</a></font>
           </td>
           <td width=86%>
             Tool to view the content of a registry key (type node).
@@ -141,7 +141,7 @@
         <tr>
 	  <td width=2%></td>
           <td width=10%>
-             <font size="3"><a href="#xml2cmp">xml2cmp</a></font>
+             <font size="3"><a href="#xml2cmp" title="link to the xml2cmp tool description">xml2cmp</a></font>
           </td>
           <td width=86%>
             A small helper tool to extract different information from xml module description files.
@@ -151,7 +151,7 @@
         <tr>
 	  <td width=2%></td>
           <td width=10%>
-             <font size="3"><a href="#unoexe">uno</a></font>
+             <font size="3"><a href="#unoexe"  title="link to the uno tool description">uno</a></font>
           </td>
           <td width=86%>
             Tool to start UNO components and provide a UNO runtime environment.
@@ -161,7 +161,7 @@
         <tr>
 	  <td width=2%></td>
           <td width=10%>
-             <font size="3"><a href="#autodoc">autodoc</a></font>
+             <font size="3"><a href="#autodoc"  title="link to the autodoc tool description">autodoc</a></font>
           </td>
           <td width=86%>
             Tool to generate javadoc-like documentation for C/C++ and UNOIDL files.
@@ -197,12 +197,12 @@
       <blockquote> 
       <p><font size="5"><b><a name="idlc">idlc</a></b></font>
         &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-        <a href="../index.html">SDK home</a>&nbsp;&nbsp;<a href="#tools">tools overview</a>
+        <a href="../index.html" title="link to the SDK start page">SDK home</a>&nbsp;&nbsp;<a href="#tools" title="link to the tools overview">tools overview</a>
       </p>
       <p>'idlc' is the UNOIDL compiler.  It is a full featured compiler used to check UNODL type definitions and
          transform valid type definitions into a binary type library format, which is later used by all
          codemaker tools. It is also used as a dynamic type library for UNO at runtime.<br>
-         You can find a syntax description for UNOIDL <a href="notsupported.html">here</a>.</p>
+         You can find a syntax description for UNOIDL <a href="DevelopersGuide/Appendix/IDLSyntax/IDLSyntax.htm#1+UNOIDL+Syntax+Specification" title="link to the IDL syntax specification in the Developer's Guide">here</a>.</p>
       <p><b>Usage:</b></p>
       <blockquote> 
       <b><code>idlc [-options] file_1 ... file_n | @&lt;filename&gt;</code></b>
@@ -288,7 +288,7 @@
       <blockquote> 
       <p><font size="5"><b><a name="cppumaker">cppumaker</a></b></font>
         &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-        <a href="../index.html">SDK home</a>&nbsp;&nbsp;<a href="#tools">tools overview</a>
+        <a href="../index.html" title="link to the SDK start page">SDK home</a>&nbsp;&nbsp;<a href="#tools" title="link to the tools overview">tools overview</a>
       </p>
       <p>The cppumaker generates a C++ representation for idl types. The cppumaker works on a typelibrary,
       	 which is generated by the unoidl. It generates the output for all specified types and for all types
@@ -403,7 +403,7 @@
       <blockquote> 
       <p><font size="5"><b><a name="javamaker">javamaker</a></b></font>
         &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-        <a href="../index.html">SDK home</a>&nbsp;&nbsp;<a href="#tools">tools overview</a>
+        <a href="../index.html" title="link to the SDK start page">SDK home</a>&nbsp;&nbsp;<a href="#tools" title="link to the tools overview">tools overview</a>
       </p>
       <p>The javamaker generates the appropriate java file for each idl type. The javamaker works
          on a typelibrary which is generated by the unoidl. It generates the output for all specified
@@ -466,7 +466,7 @@
       <blockquote> 
       <p><font size="5"><b><a name="rdbmaker">rdbmaker</a></b></font>
         &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-        <a href="../index.html">SDK home</a>&nbsp;&nbsp;<a href="#tools">tools overview</a>
+        <a href="../index.html" title="link to the SDK start page">SDK home</a>&nbsp;&nbsp;<a href="#tools" title="link to the tools overview">tools overview</a>
       </p>
       <p>The rdbmaker generates subsets of the typelibrary. The rdbmaker works on a typelibrary that
          is generated by the unoidl. It generates a subset of the typelibrary, which contains all specified
@@ -548,9 +548,9 @@
       <blockquote> 
       <p><font size="5"><b><A name="pkgchk">pkgchk (pkgchk.bin)</A></b></font>
         &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-        <a href="../index.html">SDK home</a>&nbsp;&nbsp;<a href="#tools">tools overview</a>
+        <a href="../index.html" title="link to the SDK start page">SDK home</a>&nbsp;&nbsp;<a href="#tools" title="link to the tools overview">tools overview</a>
       </p>
-      <p>'pkgchk' is a tool for easy deployment of UNO packages in an exisiting office installation. 
+      <p>'pkgchk' is a tool for easy deployment of UNO packages in an existing office installation. 
          UNO packages are UNO components (single libraries or Jar files or more complex zip files that 
          contains one or more libraries|Jar files, type libraries and configuration items) and 
          [PRODUCTNAME] libraries as zip package. More detailed information comes with the 
@@ -652,7 +652,7 @@
       <blockquote> 
       <p><font size="5"><b><A name="regcomp">regcomp</A></b></font>
         &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-        <a href="../index.html">SDK home</a>&nbsp;&nbsp;<a href="#tools">tools overview</a>
+        <a href="../index.html" title="link to the SDK start page">SDK home</a>&nbsp;&nbsp;<a href="#tools" title="link to the tools overview">tools overview</a>
       </p>
       <p>'regcomp' is a tool to register|revoke external UNO components into|from 
          a registry which is used for a UNO environment.</p>
@@ -729,11 +729,11 @@
       <blockquote> 
       <p><font size="5"><b><A name="regmerge">regmerge</A></b></font>
         &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-        <a href="../index.html">SDK home</a>&nbsp;&nbsp;<a href="#tools">tools overview</a>
+        <a href="../index.html" title="link to the SDK start page">SDK home</a>&nbsp;&nbsp;<a href="#tools" title="link to the tools overview">tools overview</a>
       </p>
       <p>'regmerge' is a small tool to merge different registry files under a specified
-         key into another registry file. If a value already exists in the targetfile
-         the value would be overwritten by the value of the sourcefile.</p>
+         key into another registry file. If a value already exists in the target file
+         the value would be overwritten by the value of the source file.</p>
       <p><b>Usage:</b></p>
       <blockquote> 
       <b><code>regmerge &lt;mergefile&gt; mergeKeyName &tg;regfile_1&gt; ... &lt;regfile_n&gt;</code></b>
@@ -764,7 +764,7 @@
           <td width=15%><code>-c&lt;locationUrls&gt;</code></td>
           <td width=85%>
             the location of an component (DLL, Class name, or an url of a jar file) or a list of urls
-            seperated by ';'s. Note, if a list of urls is specified, the components must all need the
+            separated by ';'s. Note, if a list of urls is specified, the components must all need the
             same loader.
           </td>
         </tr>
@@ -806,7 +806,7 @@
       <blockquote> 
       <p><font size="5"><b><A name="regview">regview</A></b></font>
         &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-        <a href="../index.html">SDK home</a>&nbsp;&nbsp;<a href="#tools">tools overview</a>
+        <a href="../index.html" title="link to the SDK start page">SDK home</a>&nbsp;&nbsp;<a href="#tools" title="link to the tools overview">tools overview</a>
       </p>
       <p>'regview' is a tool to show the contents of a registry file. The tool dumps the hierarchical
          structure and the values of the nodes to stdout in a readable form.</p>
@@ -861,7 +861,7 @@
       <blockquote> 
       <p><font size="5"><b><a name="xml2cmp">xml2cmp</a></b></font>
         &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-        <a href="../index.html">SDK home</a>&nbsp;&nbsp;<a href="#tools">tools overview</a>
+        <a href="../index.html" title="link to the SDK start page">SDK home</a>&nbsp;&nbsp;<a href="#tools" title="link to the tools overview">tools overview</a>
       </p>
       <p>The tool xml2cmp parses .xml files, which contain the descriptions of components that implement
          UNO services. Each .xml file refers to one library. The library may contain one or more component 
@@ -962,7 +962,7 @@
       <blockquote> 
       <p><font size="5"><b><a name="unoexe">uno</a></b></font>
         &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-        <a href="../index.html">SDK home</a>&nbsp;&nbsp;<a href="#tools">tools overview</a>
+        <a href="../index.html" title="link to the SDK start page">SDK home</a>&nbsp;&nbsp;<a href="#tools" title="link to the tools overview">tools overview</a>
       </p>
       <p>The UNO-starter is for running a component or service process, and providing a runtime environment.
          Raising a component might look like this </p>
@@ -970,7 +970,7 @@
       <p>or</p>
       <p><code>[c:\] uno.exe -s foo.bar.FooBarService -r myregistry.rdb -- foo bar </code> </p>
       <p>The starter loads the component and instantiates it. The component must export the interface
-         <a href="common/ref/com/sun/star/lang/XMain.html">com.sun.star.lang.XMain</a>:</p>
+         <a href="common/ref/com/sun/star/lang/XMain.html" title="link into the IDL reference to the interface com.sun.star.lang.XMain">com.sun.star.lang.XMain</a>:</p>
       <p><code>interface XMain : com::sun::star::uno::XInterface <br>
                { <br>
                  &nbsp;&nbsp;&nbsp; /** This method is called to run the component.<br>
@@ -1041,7 +1041,7 @@
             </td>
           </tr>
         </table>
-        <p><b>Service <a href="common/ref/com/sun/star/bridge/UnoUrlResolver.html">
+        <p><b>Service <a href="common/ref/com/sun/star/bridge/UnoUrlResolver.html" title="link into the IDL reference to the service com.sun.star.bridge.UnoUrlResolver">
                          com.sun.star.bridge.UnoUrlResolver</a></b></p>
         <p>You can easily connect to a server started with the -u (url) option by using this service, giving
 	   the same url to resolve. The service provides you an instance from remote.</p>
@@ -1075,12 +1075,12 @@
       <blockquote> 
       <p><font size="5"><b><a name="autodoc">autodoc</a></b></font>
         &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-        <a href="../index.html">SDK home</a>&nbsp;&nbsp;<a href="#tools">tools overview</a>
+        <a href="../index.html" title="link to the SDK start page">SDK home</a>&nbsp;&nbsp;<a href="#tools" title="link to the tools overview">tools overview</a>
       </p>
       <p>The autodoc tool is used for creating javadoc-like documentation from C++ and UNOIDL source code.</p>
       <p>There are some conventions to follow when documenting C++- or UNOIDL-sourcecode. See &nbsp;
          (( REFERENCE to commenting guides for C++ and IDL )). &nbsp;<br>
-         If you are not familiar with these, but do know Javadoc: For simple C++ &nbsp;sourcecode documentation, 
+         If you are not familiar with these, but do know javadoc: For simple C++ &nbsp;sourcecode documentation, 
          using javadoc-style comments will work.<br>
       </p>
       <p><b>Usage:</b></p>