xml-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rah...@locus.apache.org
Subject cvs commit: xml-site/sources/xerces-c faq-distrib.xml
Date Fri, 17 Dec 1999 19:24:35 GMT
rahulj      99/12/17 11:24:35

  Modified:    sources/xerces-c faq-distrib.xml
  Log:
  Clarified what needs to be included in the Xerces-C distributions.
  
  Revision  Changes    Path
  1.6       +44 -7     xml-site/sources/xerces-c/faq-distrib.xml
  
  Index: faq-distrib.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/xerces-c/faq-distrib.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- faq-distrib.xml	1999/12/15 01:02:40	1.5
  +++ faq-distrib.xml	1999/12/17 19:24:35	1.6
  @@ -6,19 +6,56 @@
   <faq title="Which DLL's do I need to distribute with my application?">
   
   <q>Which DLL's do I need to distribute with my application?</q>
  +
   <a>
  -<p>The current &XercesCProjectName; distribution contains TWO shared
  -libraries, &XercesCWindowsLib;.dll and icuuc.dll. To distribute
  -your application, you will need to distribute these two
  -DLLs along with your own. On AIX the shared library name
  -is &XercesCUnixLib;.a and libicu-uc.a, on Solaris/Linux it is
  -called &XercesCUnixLib;.so and libicu-uc.so while on HP-UX it
  -is called &XercesCUnixLib;.sl and libicu-uc.sl.</p>
  +<p>There are currently two configurations in which Xerces-C binaries
  +are published. One is from the Apache site, while the other is
  +from the IBM Alphaworks Site.</p>
  +
  +<p>The <jump href="http://xml.apache.org/dist">Apache download
  +site</jump> binary drops only contain support for ASCII, UTF-8, UTF-16
  +and UCS4 encodings. The parser intrinsically supports transcoding
  +input files in these encodings to Unicode (all internal processing in
  +the parser happens in Unicode).  If you are using these Xerces-C
  +binaries in your application, then you only need to distribute
  +<em>one</em> file:<br></br>
  +&XercesCWindowsLib;.dll for Windows NT/95/98, or<br></br>
  +&XercesCUnixLib;.a for AIX, or<br></br>
  +&XercesCUnixLib;.so for Solaris/Linux, or<br></br>
  +&XercesCUnixLib;.sl for HP-UX.</p>
  +
  +<p>However, if your application needs to support more international
  +encodings, other than the one's mentioned above, then you may use the
  +XML4C binaries published by IBM at their <jump
  +href="http://www.alphaworks.ibm.com/tech/xml4c">AlphaWorks</jump>
  +site.  XML4C binaries use and include <jump
  +href="http://www10.software.ibm.com/developerworks/opensource/icu/index.html">IBM
  +Classes for Unicode</jump> (ICU) (also an open source project but
  +under <jump
  +href="http://www10.software.ibm.com/developerworks/opensource/license10.html">IBM
  +Public License</jump>) for transcoding and as a result can parse input
  +files in over 100 different encodings. If you are using XML4C binaries
  +in your application, then in <em>addition</em> to the Xerces-C library
  +file mentioned above, you also need to ship:</p>
  +
  +<ol>
  +<li><em>ICU shared library file</em>:<br></br>
  +icuuc.dll for Windows NT/95/98, or<br></br>
  +libicu-uc.a for AIX, or<br></br>
  +libicu-uc.so for Solaris/Linux, or<br></br>
  +libicu-uc.sl for HP-UX.</li>
  +<li><em>ICU converter files</em>: *.cnv.<br></br>
  +These are platform specific binary files which contain the tables used
  +to transcode characters from the respective encoding to Unicode. These
  +files may be found in the 'lib/icu/data' directory of the XML4C binary
  +archives.</li>
  +</ol>
   </a>
   
   </faq>
   
   <faq title="How do I package the sources to create a binary drop?">
  +
   <q>How do I package the sources to create a binary drop?</q>
   
   <a>
  
  
  

Mime
View raw message