diff --git a/doc/build-misc.xml b/doc/build-misc.xml index b8eb53cda2ffba1c8b4734f9da3ad4541ad56be2..c20aa3e7f22c19f75456e5fbb8326d4810fc00f4 100644 --- a/doc/build-misc.xml +++ b/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> diff --git a/doc/faq-build.xml b/doc/faq-build.xml index 9d0b8ab645fc562aa4f20e939773e7f7f032a898..45060b6b638d5bcc4dcc42a5acf2f809b2e4668d 100644 --- a/doc/faq-build.xml +++ b/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> diff --git a/doc/install.xml b/doc/install.xml index b7ef27d2a6739b8de64a75a7e5e1fefe6faad9d8..b10c900730180ac221345b02b410267e4d64bae3 100644 --- a/doc/install.xml +++ b/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=<full_path_to_&XercesCInstallDir;>\lib</source> + to point to the directory, $XERCESCROOT/msg, where the message files reside.</p> +<source>SET XERCESC_NLS_HOME=<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. diff --git a/doc/samples.xml b/doc/samples.xml index 9ed6994dfa668d430629aa1b3255804068f0efa1..04ddec2306bc63e5a34f41a7d2cc1eb78aeaaef5 100644 --- a/doc/samples.xml +++ b/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