ICU 1.8.1 update
git-svn-id: https://svn.apache.org/repos/asf/xerces/c/trunk@172788 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/doc/faq-distrib.xml b/doc/faq-distrib.xml
index c4f236f..fc8969c 100644
--- a/doc/faq-distrib.xml
+++ b/doc/faq-distrib.xml
@@ -55,19 +55,18 @@
encodings, say in Shift-JIS, Big5 etc., then you cannot
use Xerces-C. XML4C addresses this need. It combines Xerces-C
and <jump
- href="http://www10.software.ibm.com/developerworks/opensource/icu/index.html">
+ href="http://oss.software.ibm.com/icu/">
International Components for Unicode (ICU)</jump> and
provides support for over 100 different encodings.</p>
<p>ICU is also an open source project but is licensed
under the <jump
- href="http://www10.software.ibm.com/developerworks/opensource/license10.html">
- IBM Public License</jump>. XML4C is published by IBM and
+ href="http://www.x.org/terms.htm">
+ X License</jump>. XML4C is published by IBM and
can be downloaded from their <jump
href="http://www.alphaworks.ibm.com/tech/xml4c">Alphaworks</jump>
site. The license to use XML4C is simply to comply with
- the Apache license (because of Xerces-C) and IBM Public
- License (because of ICU).</p>
+ the Apache license (because of Xerces-C) and X License (because of ICU).</p>
<p>XML4C binaries are published for Solaris using SunWorkshop
compiler, HPUX 10.20 and 11.0 using CC and aCC, Redhat
diff --git a/doc/program.xml b/doc/program.xml
index 6b2d06d..8ea276d 100644
--- a/doc/program.xml
+++ b/doc/program.xml
@@ -527,7 +527,7 @@
<note>The ICU classes are a more general solution to UNICODE
character handling for C++ applications. ICU is an Open
Source Unicode library, available at the <jump
- href="http://www.software.ibm.com/developerworks/opensource/icu/index.html">IBM
+ href="http://oss.software.ibm.com/icu/">IBM
DeveloperWorks website</jump>.</note>
</s3>
@@ -713,7 +713,7 @@
<anchor name="IDOMObjMemMgmt"/>
<s3 title="Objects and Memory Management">
- <p>The C++ IDOM implementation no longer uses reference counting for
+ <p>The C++ IDOM implementation no longer uses reference counting for
automatic memory management. The storage for a DOM document is
associated with the document node object. Applications would use
normal C++ pointers to directly access the implementation objects
@@ -736,7 +736,7 @@
<source>
// DOM C++
DOM_Node aNode;
-DOM_Node docRootNode;
+DOM_Node docRootNode;
aNode = someDocument.createElement("ElementName");
docRootNode = someDocument.getDocumentElement();
docRootNode.appendChild(aNode);
@@ -747,7 +747,7 @@
The advantage here is that allocation would require no synchronization
in most cases (based on the the same threading model that we
have now - one thread active per document, but any number of
- documents running in parallel with separate threads).
+ documents running in parallel with separate threads).
</p>
<p>The allocator does not support a delete operation at all - all
