From 8651474793bd4e1a843ea06698c2c421c98155ab Mon Sep 17 00:00:00 2001 From: George Rhoten Date: Thu, 17 Feb 2005 22:55:11 +0000 Subject: [PATCH] ICU-4412 Bye bye oss.software.ibm.com. Your pages have been sent to other various web sites. X-SVN-Rev: 17219 --- icu4c/readme.html | 109 ++++++++++++++++++++++++---------------------- 1 file changed, 58 insertions(+), 51 deletions(-) diff --git a/icu4c/readme.html b/icu4c/readme.html index 50924763ff..5d727ef7be 100644 --- a/icu4c/readme.html +++ b/icu4c/readme.html @@ -29,8 +29,8 @@ ICU 3.2 ReadMe -

Version: 2004-Nov-30
- Copyright © 1997-2004 International Business Machines Corporation and +

Version: 2005-Feb-17
+ Copyright © 1997-2005 International Business Machines Corporation and others. All Rights Reserved.

@@ -138,10 +138,9 @@ boundaries -

ICU has a sister project ICU4J that extends the - internationalization capabilities of Java to a level similar to ICU. The - ICU C/C++ project is also called ICU4C when a distinction is necessary.

+

ICU has a sister project ICU4J that extends the internationalization + capabilities of Java to a level similar to ICU. The ICU C/C++ project is + also called ICU4C when a distinction is necessary.

Getting started

@@ -160,59 +159,59 @@ - ICU Homepage + ICU, ICU4C, ICU4J & ICU4JNI Official Homepage http://oss.software.ibm.com/icu/index.html + "http://www.ibm.com/software/globalization/icu/index.jsp">http://www.ibm.com/software/globalization/icu/index.jsp - ICU4J Homepage + ICU, ICU4C, ICU4J & ICU4JNI Unofficial Homepage http://oss.software.ibm.com/icu4j/index.html + "http://icu.sourceforge.net/">http://icu.sourceforge.net/ FAQ - Frequently Asked Questions about ICU http://oss.software.ibm.com/icu/userguide/icufaq.html + "http://icu.sourceforge.net/userguide/icufaq.html">http://icu.sourceforge.net/userguide/icufaq.html ICU User's Guide http://oss.software.ibm.com/icu/userguide/index.html + "http://icu.sourceforge.net/userguide/">http://icu.sourceforge.net/userguide/ Download ICU Releases http://oss.software.ibm.com/icu/download/index.html + "http://www.ibm.com/software/globalization/icu/downloads.jsp">http://www.ibm.com/software/globalization/icu/downloads.jsp API Documentation Online http://oss.software.ibm.com/icu/apiref/index.html + "http://icu.sourceforge.net/apiref/index.html">http://icu.sourceforge.net/apiref/index.html Online ICU Demos http://oss.software.ibm.com/icu/demo/index.html + "http://www.ibm.com/software/globalization/icu/chartsdemostools.jsp">http://www.ibm.com/software/globalization/icu/chartsdemostools.jsp Contacts and Bug Reports/Feature Requests http://oss.software.ibm.com/icu/archives/index.html + "http://icu.sourceforge.net/contacts.html">http://icu.sourceforge.net/contacts.html @@ -255,7 +254,7 @@ versions are tested more thoroughly than day-to-day development builds of the system, and they are packaged in zip and tar files for convenient download. These packaged files can be found at http://oss.software.ibm.com/icu/download/index.html.
+ "http://www.ibm.com/software/globalization/icu/downloads.jsp">http://www.ibm.com/software/globalization/icu/downloads.jsp.
The packaged snapshots are named icu-nnnn.zip or icu-nnnn.tgz, where nnnn is the version number. The .zip @@ -269,8 +268,9 @@ ICU, you should probably be working with the latest version of the ICU source code. You will need to check the code out of our CVS repository to ensure that you have the most recent version of all of the files. See our - CVS page - for details. + CVS + page for details.

ICU Source Code @@ -279,7 +279,7 @@

In the descriptions below, <ICU> is the full path name of the ICU directory (the top level directory from the distribution archives) in your file system. You can also view the ICU Architectural + "http://icu.sourceforge.net/userguide/design.html">ICU Architectural Design section of the User's Guide to see which libraries you need for your software product. You need at least the data ([lib]icudt) and the common ([lib]icuuc) libraries in order to use ICU.

@@ -397,7 +397,7 @@ environment variable to the out/ or the out/build/ directories, but this is generally discouraged because most people set it incorrectly. You can view the ICU Data + "http://icu.sourceforge.net/userguide/icudata.html">ICU Data Management section of the ICU User's Guide for details.

@@ -823,8 +823,8 @@ file in Microsoft Visual Studio .NET 2003. (This solution includes all the International Components for Unicode libraries, necessary ICU building tools, and the test suite projects). Please see the command line note below if you want to - build from the command line instead. + "#HowToBuildWindowsCommandLine">command line note below if you want + to build from the command line instead.
  • Set the active configuration to "Debug" or "Release" (See Windows configuration note below).
    • @@ -1106,7 +1106,8 @@ the current location). HP-UX user's, please see this note regarding HP-UX multithreaded build issues with newer compilers. Solaris user's, please see this note regarding Solaris multithreaded build issues.

    + "#ImportantNotesSolaris">note regarding Solaris multithreaded build + issues.

    Running The Tests From The Command Line @@ -1313,7 +1314,8 @@ Data set name type : PDS

    How To Build And Install On i5/OS (OS/400 iSeries)

    + "HowToBuildOS400">How To Build And Install On i5/OS (OS/400 + iSeries)

    Before you start building ICU, ICU requires the following:

    @@ -1427,9 +1429,9 @@ ADDENVVAR ENVVAR(OUTPUTDIR) VALUE('libraryname') need. On operating systems that do not have a standard C++ ABI (name mangling) for compilers, it is recommended to do this special packaging anyway. More details on customizing ICU are available in the User's Guide. - The ICU Source Code Organization section of this - readme.html gives a more complete description of the libraries.

    + "http://icu.sourceforge.net/userguide/">User's Guide. The ICU Source Code Organization section of this readme.html + gives a more complete description of the libraries.

    @@ -1456,7 +1458,7 @@ ADDENVVAR ENVVAR(OUTPUTDIR) VALUE('libraryname') @@ -1589,15 +1591,17 @@ ADDENVVAR ENVVAR(OUTPUTDIR) VALUE('libraryname')
    Solaris Deadlock Issues in Solaris 8 (2.8) and Earlier

    Solaris 8, and earlier, has outstanding thread deadlocking issues that - may be problematic for applications using either native, or POSIX, - threading on these platforms. Sun states that Solaris 9 does not have the - deadlock problems. Deadlocks may occur either during initialization of the - Solaris threading library, or at any other time.

    + may be problematic for applications using either native, + or POSIX, threading on these platforms. Sun states that Solaris 9 + does not have the deadlock problems. Deadlocks + may occur either during initialization of the Solaris + threading library, or at any other time.

    Sun Microsystems has provided a Sun Alert Notification regarding the - issue. Users should consider applying the latest OS patches to their - Solaris installations in order to help avoid deadlock. Further information - regarding the issue, and links to applicable patches, may be found at:

    + issue. Users should consider applying the latest OS + patches to their Solaris installations in order to help avoid deadlock. + Further information regarding the issue, and links to applicable patches, + may be found at:

    [1] "Applications Linked to libthread May Hang", Sun Alert Notification, Sun Microsystems, Inc., 04-Sep-2002
    @@ -1605,23 +1609,25 @@ ADDENVVAR ENVVAR(OUTPUTDIR) VALUE('libraryname') "http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fsalert%2F46867&zone_32=4663077"> http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fsalert%2F46867&zone_32=4663077

    -

    Sun is not providing patches for Solaris 6 (2.6), or earlier.

    +

    Sun is not providing patches for Solaris 6 (2.6), or + earlier.

    Sun states that by applying the patch users will avoid the deadlock - issues. However, with all applicable patches applied, deadlock may still be - seen, as demonstrated by the ICU Mutex unit tests. The unit test will hang - indefinitely. No bug exists in ICU. However, a latent bug still exists in - Solaris, which Sun Microsystems has yet to resolve. In order to avoid this, - users are suggested to modify their LD_LIBRARY_PATH according to the - guidelines specified by Sun Microsystems in the Sun Alert Notification.

    + issues. However, with all applicable patches applied, deadlock + may still be seen, as demonstrated by the ICU Mutex unit + tests. The unit test will hang indefinitely. No bug exists in ICU. However, + a latent bug still exists in Solaris, which Sun Microsystems has yet to + resolve. In order to avoid this, users are suggested to + modify their LD_LIBRARY_PATH according to the guidelines specified by Sun + Microsystems in the Sun Alert Notification.

    Linking on Solaris

    In order to avoid synchronization and threading issues, developers are - suggested to strictly follow the compiling and linking guidelines for - multithreaded applications, specified in the following document from Sun - Microsystems. Most notably, pay strict attention to the following - statements from Sun:

    + suggested to strictly follow the compiling and linking + guidelines for multithreaded applications, specified in the following + document from Sun Microsystems. Most notably, pay strict attention to the + following statements from Sun:

    To use libthread, specify -lthread before -lc on the ld command line, @@ -1719,7 +1725,7 @@ ADDENVVAR ENVVAR(OUTPUTDIR) VALUE('libraryname')

    If you are using ICU's Makefiles to build ICU on a new platform, there are a few places where you will need to add or modify some files. If you need more help, you can always ask the icu4c-support mailing list. + "http://icu.sourceforge.net/contacts.html">icu4c-support mailing list. Once you have finished porting ICU to a new platform, it is recommended that you contribute your changes back to ICU via the icu4c-support mailing list. This will make it easier for everyone to benefit from your work.

    @@ -1735,7 +1741,7 @@ ADDENVVAR ENVVAR(OUTPUTDIR) VALUE('libraryname') share the same endianness and the same charset family. This assertion does not include platform dependent DLLs/shared/static libraries. For details see the User Guide ICU Data + "http://icu.sourceforge.net/userguide/icudata.html">ICU Data chapter.

    ICU 2.8 removes the requirement that ICU be completely built in the @@ -1799,7 +1805,8 @@ ADDENVVAR ENVVAR(OUTPUTDIR) VALUE('libraryname')

    • XP_CPLUSPLUS for C++ only.
      • -
    • Generic types like UBool, int8_t, int16_t, int32_t, int64_t, uint64_t etc.
      • +
    • Generic types like UBool, int8_t, int16_t, int32_t, int64_t, + uint64_t etc.
    • U_EXPORT and U_IMPORT for specifying dynamic library import and export
      • @@ -1919,7 +1926,7 @@ ADDENVVAR ENVVAR(OUTPUTDIR) VALUE('libraryname')
      -

      Copyright © 1997-2004 International Business Machines Corporation +

      Copyright © 1997-2005 International Business Machines Corporation and others. All Rights Reserved.
      IBM Globalization Center of Competency - San José
      5600 Cottle Road

    Data required by the Common and I18n libraries. There are many ways to package and customize this + "http://icu.sourceforge.net/userguide/icudata.html">customize this data, but by default this is all you need.