diff --git a/icu4c/readme.html b/icu4c/readme.html index dd2f980a44..88ca314fc5 100644 --- a/icu4c/readme.html +++ b/icu4c/readme.html @@ -32,7 +32,7 @@ ICU 2.6 ReadMe -

Version: 2003-Feb-11
+

Version: 2003-Apr-14
Copyright © 1997-2003 International Business Machines Corporation and others. All Rights Reserved.

@@ -598,7 +598,7 @@ - HP/UX 11.01 + HP-UX 11.01 aCC A.12.10
cc A.11.01.00 @@ -693,12 +693,12 @@ CygWin gcc 2.95.3 - + Rarely tested - HP/UX 11.01 + HP-UX 11.01 CC A.03.10 @@ -1223,9 +1223,9 @@ ADDENVVAR ENVVAR(OUTPUTDIR) VALUE('libraryname')
  • Change your current directory to icu/source.
  • -
  • Run 'export CFLAGS=-O4 CXXFLAGS=-O4' to optimize your - build of ICU. If the build fails, rerun these build steps without this - step before asking the icu4c-support mailing list for help.
  • +
  • Run 'export CFLAGS=-O4 CXXFLAGS=-O4' to optimize your build + of ICU. If the build fails, rerun these build steps without this step + before asking the icu4c-support mailing list for help.
  • Run 'cp ../as_is/os400/configure .'
  • @@ -1288,11 +1288,12 @@ del common/libicuuc.o products. Usually only the libraries need to be considered for packaging.

    -

    On Unix, you should have used "gmake install" to make it easier to - develop and package ICU. The bin, lib and include directories are needed to - develop applications that use ICU. These directories will be created relative to the - "--prefix=dir" configure option (See above). - When ICU is built on Windows, a similar directory structure is built.

    +

    On Unix, you should have used "gmake install" to make it easier + to develop and package ICU. The bin, lib and include directories are needed + to develop applications that use ICU. These directories will be created + relative to the "--prefix=dir" configure option (See above). When ICU is built on Windows, a similar + directory structure is built.

    When changes have been made to the standard ICU distribution, it is recommended that at least one of the following guidelines be followed for @@ -1403,8 +1404,18 @@ del common/libicuuc.o chance that the ICU global mutex is not initialized properly. Normally the ICU global mutex is initialized during C++ static initialization, but there are some compilers and linkers that do not properly perform C++ static - initialization in a library (this sometimes happens on HP/UX and on MacOS - 10.1).

    + initialization in a library. Here are some of the cases when the global + mutex is not initialized:

    + +

    Upon the first usage of most ICU APIs, the global mutex will get initialized. For example, you could call uloc_countAvailable() or @@ -1416,8 +1427,9 @@ del common/libicuuc.o initialization works properly.

    ICU does not use C++ static initialization for anything else, and - disabling threads in ICU will disable all C++ static initialization in - ICU.

    + disabling threads in ICU will disable all C++ static initialization in ICU. + If you do not have a multithreaded application, you do not need to worry + about the global mutex.

    How to Make ICU Smaller

    @@ -1588,9 +1600,9 @@ del common/libicuuc.o
  • U_EXPORT and U_IMPORT for specifying dynamic library import and export
  • -
  • int64_t and uint64_t. If the platform does not support 64 bit values, the macro - U_INT64_T_UNAVAILABLE must be defined. For example, this will disable - Rule-based number formatting.
  • +
  • int64_t and uint64_t. If the platform does not support 64 bit + values, the macro U_INT64_T_UNAVAILABLE must be defined. For + example, this will disable Rule-based number formatting.