$XERCESCROOT/msg created as home directory for message files.

git-svn-id: https://svn.apache.org/repos/asf/xerces/c/trunk@174478 13f79535-47bb-0310-9956-ffa450edef68

doc/build-misc.xml

@@ -80,7 +80,7 @@ perl packageBinaries.pl -s x:\&XercesCSrcInstallDir; -o x:\temp\&XercesCInstallD
 
         <p>If the parser is built with icu message loader (as mentioned above), or message 
          catalog loader, you need an environment variable, XERCESC_NLS_HOME to point to
-         the directory, $XERCESCROOT/lib, where the message files reside.
+         the directory, $XERCESCROOT/msg, where the message files reside.
         </p>
         
         <p>For a description of options available, you can enter:</p>
@@ -134,7 +134,7 @@ perl packageBinaries.pl -s $HOME/&XercesCSrcInstallDir; -o $HOME/temp/&XercesCIn
 
         <p>If the parser is built with icu message loader (as mentioned above), or message 
          catalog loader, you need an environment variable, XERCESC_NLS_HOME to point to
-         the directory, $XERCESCROOT/lib, where the message files reside.
+         the directory, $XERCESCROOT/msg, where the message files reside.
         </p>
                 
         </s3>

doc/faq-build.xml

@@ -295,7 +295,7 @@ catch (const XMLException& toCatch) {
     <a>
       <p>If the parser is built with icu message loader (like IBM XML4C binaries), or message 
          catalog loader, you need an environment variable, XERCESC_NLS_HOME to point to
-         the directory, $XERCESCROOT/lib, where the message files reside.
+         the directory, $XERCESCROOT/msg, where the message files reside.
       </p>
     </a>
   </faq>

doc/install.xml

@@ -41,8 +41,8 @@
 
         <p>Besides, if the parser is built with icu message loader (like IBM XML4C binaries),
         or message catalog loader, then you need to create a new environment variable, XERCESC_NLS_HOME
-        to point to the directory, $XERCESCROOT/lib, where the message files reside.</p>           
-<source>SET XERCESC_NLS_HOME=&lt;full_path_to_&XercesCInstallDir;>\lib</source>
+        to point to the directory, $XERCESCROOT/msg, where the message files reside.</p>           
+<source>SET XERCESC_NLS_HOME=&lt;full_path_to_&XercesCInstallDir;>\msg</source>
            
         <p>The binary distribution has the built parser library and some samples executables.
            Please refer to the <jump href="samples.html">Samples</jump> for how to run the samples.</p>
@@ -112,11 +112,11 @@ setenv SHLIB_PATH "$XERCESCROOT/lib:$SHLIB_PATH" (on HP-UX)</source>
 
         <p>Besides, if the parser is built with icu message loader (like IBM XML4C binaries),
         or message catalog loader, then you need to create a new environment variable, XERCESC_NLS_HOME
-        to point to the directory, $XERCESCROOT/lib, where the message files reside.</p>                     
+        to point to the directory, $XERCESCROOT/msg, where the message files reside.</p>                     
 <source>
-export XERCESC_NLS_HOME=$XERCESCROOT/lib
+export XERCESC_NLS_HOME=$XERCESCROOT/msg
 or
-setenv XERCESC_NLS_HOME=$XERCESCROOT/lib
+setenv XERCESC_NLS_HOME=$XERCESCROOT/msg
 </source>        
 
         <p>The binary distribution has the built parser library and some samples executables.

doc/samples.xml

@@ -34,14 +34,14 @@
 
                <p>On both Windows and UNIX platforms, if the parser is built with icu message loader
                (like IBM XML4C binaries), or message catalog loader, then you need to set another environment
-               variable, XERCESC_NLS_HOME to point to the directory, $XERCESCROOT/lib, where the message
+               variable, XERCESC_NLS_HOME to point to the directory, $XERCESCROOT/msg, where the message
                files reside.              
                </p>
 <source>
-set XERCESC_NLS_HOME=$XERCESCROOT\lib
+set XERCESC_NLS_HOME=$XERCESCROOT\msg
 or
-export XERCESC_NLS_HOME=$XERCESCROOT/lib
-setenv XERCESC_NLS_HOME=$XERCESCROOT/lib
+export XERCESC_NLS_HOME=$XERCESCROOT/msg
+setenv XERCESC_NLS_HOME=$XERCESCROOT/msg
 </source>
                
                <p>Once you have set up the environment variables, you can run the