peiyongz 2002/11/22 13:34:30
Modified: c/doc samples.xml program.xml program-others.xml
install.xml faq-distrib.xml faq-build.xml
build-misc.xml
Log:
icumsgloader/msgcatalogloader/locale
Revision Changes Path
1.18 +4 -2 xml-xerces/c/doc/samples.xml
Index: samples.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/samples.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- samples.xml 21 Nov 2002 20:11:02 -0000 1.17
+++ samples.xml 22 Nov 2002 21:34:29 -0000 1.18
@@ -32,8 +32,10 @@
<p>To set you LIBPATH (on AIX for example), you would type:</p>
<source>export LIBPATH=&XercesCInstallDir;/lib:$LIBPATH</source>
- <p>On both Windows and UNIX platforms, you may need to set another
environment
- variable, XERCESC_NLS_HOME.
+ <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
+ files reside.
</p>
<source>
set XERCESC_NLS_HOME=$XERCESCROOT\lib
1.33 +1 -0 xml-xerces/c/doc/program.xml
Index: program.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/program.xml,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- program.xml 8 Nov 2002 15:55:56 -0000 1.32
+++ program.xml 22 Nov 2002 21:34:29 -0000 1.33
@@ -80,6 +80,7 @@
<li><jump href="program-others.html#PluggableTranscoders">Pluggable
Transcoders</jump></li>
<li><jump href="program-others.html#PortingGuidelines">Porting
Guidelines</jump></li>
<li><jump href="program-others.html#CPPNamespace">Using C++
Namespace</jump></li>
+ <li><jump href="program-others.html#SpecifylocaleforMessageLoader">Specify
locale for Message Loader</jump></li>
</ul>
</s2>
1.9 +1 -1 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.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- program-others.xml 21 Nov 2002 20:11:02 -0000 1.8
+++ program-others.xml 22 Nov 2002 21:34:29 -0000 1.9
@@ -463,7 +463,7 @@
<source>
...
- // Initialize the XML4C system
+ // Initialize the parser system
try
{
XMLPlatformUtils::Initialize("fr_FR");
1.8 +6 -2 xml-xerces/c/doc/install.xml
Index: install.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/install.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- install.xml 21 Nov 2002 20:11:02 -0000 1.7
+++ install.xml 22 Nov 2002 21:34:29 -0000 1.8
@@ -39,7 +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>
+ <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>
<p>The binary distribution has the built parser library and some samples
executables.
@@ -108,7 +110,9 @@
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>
+ <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>
export XERCESC_NLS_HOME=$XERCESCROOT/lib
or
1.27 +3 -1 xml-xerces/c/doc/faq-distrib.xml
Index: faq-distrib.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/faq-distrib.xml,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- faq-distrib.xml 8 Nov 2002 15:55:56 -0000 1.26
+++ faq-distrib.xml 22 Nov 2002 21:34:29 -0000 1.27
@@ -85,7 +85,9 @@
and <jump
href="http://oss.software.ibm.com/icu/";>
International Components for Unicode (ICU)</jump> and
- provides support for over 100 different encodings.</p>
+ provides support for over 100 different encodings.
+ XML4C also uses ICU Resource Bundle to load the messages.
+ </p>
<p>ICU is also an open source project but is licensed
under the <jump
1.10 +3 -4 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.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- faq-build.xml 21 Nov 2002 20:11:02 -0000 1.9
+++ faq-build.xml 22 Nov 2002 21:34:29 -0000 1.10
@@ -293,10 +293,9 @@
<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>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.
</p>
</a>
</faq>
1.13 +11 -1 xml-xerces/c/doc/build-misc.xml
Index: build-misc.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/build-misc.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- build-misc.xml 11 Nov 2002 22:19:46 -0000 1.12
+++ build-misc.xml 22 Nov 2002 21:34:29 -0000 1.13
@@ -78,6 +78,11 @@
will build both ICU and &XercesCName;, and copy the files (relevant to the
binary
drop) to the target directory.</p>
+ <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.
+ </p>
+
<p>For a description of options available, you can enter:</p>
<source>perl packageBinaries.pl</source>
</s3>
@@ -126,7 +131,12 @@
otherwise, the two-step build, requires set extra environment variable in
between the ICU build and
the &XercesCName; build.
</p>
-
+
+ <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.
+ </p>
+
</s3>
</s2>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
