peiyongz 2002/11/21 12:11:02
Modified: c/doc samples.xml program-others.xml migration.xml
install.xml faq-build.xml
Log:
message loader and locale
Revision Changes Path
1.17 +11 -1 xml-xerces/c/doc/samples.xml
Index: samples.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/samples.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- samples.xml 21 May 2002 18:17:57 -0000 1.16
+++ samples.xml 21 Nov 2002 20:11:02 -0000 1.17
@@ -32,7 +32,17 @@
<p>To set you LIBPATH (on AIX for example), you would type:</p>
<source>export LIBPATH=&XercesCInstallDir;/lib:$LIBPATH</source>
- <p>Once you have set up your PATH variable, you can run the
+ <p>On both Windows and UNIX platforms, you may need to set another
environment
+ variable, XERCESC_NLS_HOME.
+ </p>
+<source>
+set XERCESC_NLS_HOME=$XERCESCROOT\lib
+or
+export XERCESC_NLS_HOME=$XERCESCROOT/lib
+setenv XERCESC_NLS_HOME=$XERCESCROOT/lib
+</source>
+
+ <p>Once you have set up the environment variables, you can run the
samples by opening a command window (or your shell prompt for
UNIX environments).</p>
1.8 +33 -3 xml-xerces/c/doc/program-others.xml
Index: program-others.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/program-others.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- program-others.xml 8 Nov 2002 15:55:56 -0000 1.7
+++ program-others.xml 21 Nov 2002 20:11:02 -0000 1.8
@@ -236,9 +236,9 @@
message loading services can be derived. Your platform driver
file can create whichever type of message loader it wants to
use on that platform. &XercesCName; currently has versions for the in
- memory format, the Win32 resource format, and the message
- catalog format. An ICU one is present but not implemented
- yet. Some of the platforms can support multiple message
+ memory format, the Win32 resource format, the message
+ catalog format, and ICU message loader.
+ Some of the platforms can support multiple message
loaders, in which case a #define token is used to control
which one is used. You can set this in your build projects to
control the message loader type used.</p>
@@ -445,4 +445,34 @@
</source>
</s2>
+
+ <anchor name="SpecifyLocaleForMessageLoader"/>
+ <s2 title="Specify locale for message loader">
+
+ <p>The &XercesCName; has implemented mechanism to support NLS, though
+ the current drop has only English version message file, it is capable
+ to support other languages once the translated version of the target
+ language is available.</p>
+
+ <p>Application can specify the locale for the message loader in their
+ very first invocation to XMLPlatformUtils::Initialize() by supplying
+ a parameter for the target locale intended. The defaul locale is "en_US".
+ </p>
+ </s2>
+
+<source>
+
+...
+ // Initialize the XML4C system
+ try
+ {
+ XMLPlatformUtils::Initialize("fr_FR");
+ }
+
+ catch ()
+ {
+ }
+..
+</source>
+
</s1>
1.37 +3 -1 xml-xerces/c/doc/migration.xml
Index: migration.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/migration.xml,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -r1.36 -r1.37
--- migration.xml 8 Nov 2002 15:28:02 -0000 1.36
+++ migration.xml 21 Nov 2002 20:11:02 -0000 1.37
@@ -67,7 +67,9 @@
<anchor name="ModifiedAPI220"/>
<s4 title="Modified Public API">
<ul>
- <li>.</li>
+ <li> XMLPlatformUtils::Initialize() takes a parameter specifying
locale
+ for message loader, with default value "en_US".
+ .</li>
</ul>
</s4>
1.7 +10 -0 xml-xerces/c/doc/install.xml
Index: install.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/install.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- install.xml 1 Apr 2002 21:10:43 -0000 1.6
+++ install.xml 21 Nov 2002 20:11:02 -0000 1.7
@@ -39,6 +39,9 @@
<source>SET PATH=<full_path_to_&XercesCInstallDir;>\bin;%PATH%</source>
<p>or run the <code>SET PATH</code> command in your shell window.</p>
+ <p>Besides, you need to create a new environment variable,
XERCESC_NLS_HOME.</p>
+<source>SET XERCESC_NLS_HOME=<full_path_to_&XercesCInstallDir;>\lib</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>
@@ -104,6 +107,13 @@
setenv LIBPATH "$XERCESCROOT/lib:$LIBPATH" (on AIX)
setenv LD_LIBRARY_PATH "$XERCESCROOT/lib:$LD_LIBRARY_PATH" (on Solaris, Linux)
setenv SHLIB_PATH "$XERCESCROOT/lib:$SHLIB_PATH" (on HP-UX)</source>
+
+ <p>Besides, you need to create a new environment variable,
XERCESC_NLS_HOME.</p>
+<source>
+export XERCESC_NLS_HOME=$XERCESCROOT/lib
+or
+setenv XERCESC_NLS_HOME=$XERCESCROOT/lib
+</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>
1.9 +11 -0 xml-xerces/c/doc/faq-build.xml
Index: faq-build.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/faq-build.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- faq-build.xml 8 Nov 2002 15:28:02 -0000 1.8
+++ faq-build.xml 21 Nov 2002 20:11:02 -0000 1.9
@@ -290,4 +290,15 @@
</a>
</faq>
+ <faq title="Cannot load message domain, Xerces Panic Error">
+ <q>"Cannot load message domain, Xerces Panic Error"?</q>
+ <a>
+ <p>
+ When the library is built with icu message loader, or message catalog
loader,
+ you need an environment variable, XERCESC_NLS_HOME to point to
+ the directory, $XERCESCROOT/lib.
+ </p>
+ </a>
+ </faq>
+
</faqs>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
