diff --git a/icu4c/readme.html b/icu4c/readme.html index 019a0a7976e..ffa551e0042 100644 --- a/icu4c/readme.html +++ b/icu4c/readme.html @@ -1,16 +1,18 @@ - + - + ReadMe for ICU + "Copyright (c) 1997-2006 IBM Corporation and others. All Rights Reserved." /> + "ICU; International Components for Unicode; ICU4C; what's new; readme; read me; introduction; downloads; downloading; building; installation;" /> - + "The introduction to the International Components for Unicode with instructions on building, installation, usage and other information about ICU." /> + -

International Components for Unicode
+

International Components for Unicode
ICU 3.6 ReadMe

-

Version: 2006-Jul-15
+

Version: 2006-Aug-31
Copyright © 1997-2006 International Business Machines Corporation and others. All Rights Reserved.

-
+

Table of Contents

@@ -92,7 +95,7 @@ -
+

Introduction

@@ -140,7 +143,7 @@ "GettingStarted">Getting started

This document describes how to build and install ICU on your machine. For - other information about ICU please see the following table of links.
+ other information about ICU please see the following table of links.
The ICU homepage also links to related information about writing internationalized software.

@@ -220,19 +223,21 @@ "http://www.ibm.com/software/globalization/icu/downloads.jsp">ICU 3.6 download page.

-

Changes to - packaging resource bundles

+

Changes to packaging + resource bundles

Since ICU 3.0, the old style of packaging was deprecated, and an alternate - packaging mode was made available. In this release, this compatibility mode of - packaging has been removed from ICU. If you're using the genrb -P or -t options, - you are probably using the older compatible mode of data packaging. This - compatibility file naming mode was removed for portability and performance reasons.

- -

Code changes should not be required to use the newer data file naming scheme, - but you will need to update your makefile scripts, if you're using the older - data file naming scheme. The example of using the new data file naming scheme - can be found in the ufortune sample program.

+ packaging mode was made available. In this release, this compatibility mode + of packaging has been removed from ICU. If you're using the genrb -P or -t + options, you are probably using the older compatible mode of data packaging. + This compatibility file naming mode was removed for portability and + performance reasons.

+ +

Code changes should not be required to use the newer data file naming + scheme, but you will need to update your makefile scripts, if you're using + the older data file naming scheme. The example of using the new data file + naming scheme can be found in the ufortune + sample program.

@@ -270,8 +275,19 @@ use the C++ API of ICU, you are not affected by this change.

If you receive any errors while linking ICU into your project, please make - sure that you have set "Treat wchar_t as Built-in Type" to "Yes (/Zc:wchar_t)" - in your project files.

+ sure that you have set "Treat wchar_t as Built-in Type" to "Yes + (/Zc:wchar_t)" in your project files.

+ +

Changes to scanf and storing + floating point types

+ +

In order to improve interoperability with standard scanf implementations, + the icuio library's implementations of scanf has changed the default scanf + type from double to float. This is a breaking change + requires you to change your code if you are using the icuio library's scanf + to read double or float values with %e, %f or %g. As a + reminder, these scanf functions in the icuio library are still marked + draft.

Source download contains .dat package for ICU data

@@ -289,22 +305,22 @@

There are two ways to download ICU releases:

-


+


@@ -491,7 +507,7 @@ - - @@ -755,7 +771,7 @@
<ICU>/packaging/
+ 		<ICU>/packaging/
<ICU>/debian/		 These directories contain scripts and tools for packaging the final @@ -588,7 +604,7 @@
HP-UX 11.11aCC A.03.50
+ 		aCC A.03.50
cc B.11.11.08		 Reference platform
-


+


Key to testing frequency

@@ -1495,14 +1511,13 @@ ADDENVVAR ENVVAR(OUTPUTDIR) VALUE('libraryname')

If you are building ICU with a newer aCC compiler and you are planning on using the older <iostream.h> instead of the newer <iostream>, you will need to use a special configure flag before building ICU. By default, - the aCC - -AA flag is used on HP-UX when the compiler supports that option in order - to make ICU thread safe with RogueWave and other libraries using the 2.0 - Standard C++ library. Your applications that use ICU will also need to use - the - -AA compiler flag. To turn off this behavior in ICU, you will need to use - the --with-iostream= old configure option when you first use - runConfigureICU.

+ the aCC -AA + flag is used on HP-UX when the compiler supports that option in order to make + ICU thread safe with RogueWave and other libraries using the 2.0 Standard C++ + library. Your applications that use ICU will also need to use the -AA compiler flag. + To turn off this behavior in ICU, you will need to use the --with-iostream= + old configure option when you first use runConfigureICU.

Using ICU in a Multithreaded Environment on @@ -1540,10 +1555,9 @@ ADDENVVAR ENVVAR(OUTPUTDIR) VALUE('libraryname') found at:

[1] "Applications Linked to libthread May Hang", Sun Alert - Notification, Sun Microsystems, Inc., 04-Sep-2002
+ Notification, Sun Microsystems, Inc., 04-Sep-2002
 - http://sunsolve.sun.com/search/document.do?assetkey=1-26-46867

+ "http://sunsolve.sun.com/search/document.do?assetkey=1-26-46867">http://sunsolve.sun.com/search/document.do?assetkey=1-26-46867

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

@@ -1577,7 +1591,7 @@ ADDENVVAR ENVVAR(OUTPUTDIR) VALUE('libraryname') failure, and deadlock.

[2] "Solaris Multithreaded Programming Guide, Compiling and - Debugging", Sun Microsystems, Inc., Apr 2004
+ Debugging", Sun Microsystems, Inc., Apr 2004
http://docs.sun.com/db/doc/806-6867/6jfpgdcob?a=view

@@ -1688,7 +1702,7 @@ ADDENVVAR ENVVAR(OUTPUTDIR) VALUE('libraryname')

Try to follow the build steps from the UNIX build instructions. If the configure script fails, then you will need to modify some files. Here are the usual steps for porting to a new - platform:

+ platform:

  1. Create an mh file in icu/source/config/. You can use mh-linux or a @@ -1721,10 +1735,10 @@ ADDENVVAR ENVVAR(OUTPUTDIR) VALUE('libraryname')
    • - unicode/platform.h.in (autoconf'ed platforms)
      + unicode/platform.h.in (autoconf'ed platforms)
      unicode/pXXXX.h (others: pwin32.h, pmacos.h, ..): - Platform-dependent typedefs and defines:
      -
      + Platform-dependent typedefs and defines:
      +
      • XP_CPLUSPLUS for C++ only.
        • @@ -1736,13 +1750,13 @@ ADDENVVAR ENVVAR(OUTPUTDIR) VALUE('libraryname') export
      • <iostream> usability
        • -

      +

  2. unicode/putil.h, putil.c: platform-dependent - implementations of various functions that are platform dependent:
    -
    + implementations of various functions that are platform dependent:
    +
    • uprv_isNaN, uprv_isInfinite, uprv_getNaN and uprv_getInfinity for @@ -1758,7 +1772,7 @@ ADDENVVAR ENVVAR(OUTPUTDIR) VALUE('libraryname')
    • uprv_getDefaultCodepage for getting the default codepage encoding.
      • -

    +
  3. @@ -1767,31 +1781,31 @@ ADDENVVAR ENVVAR(OUTPUTDIR) VALUE('libraryname') for Unicode in a multithreaded application, you must provide a synchronization primitive that the classes can use to protect their global data against simultaneous modifications. See Users' guide for more - information.
    -
    + information.
    +
    • We supply sample implementations for Windows, Sun Solaris, Linux, AIX, HP-UX, BSD, Mac OS X, z/OS and many others.
      • -

    +
  4. umapfile.h, umapfile.c: functions for mapping or otherwise reading or loading files into memory. All access by ICU to data - from files makes use of these functions.
    -
    5. + from files makes use of these functions.
    +
  5. Using platform specific #ifdef macros are highly discouraged outside of the scope of these files. When the source code gets updated in the future, these #ifdef's can cause testing problems for your platform.
    6. -
    +

    Copyright © 1997-2006 International Business Machines Corporation and - others. All Rights Reserved.
    - IBM Globalization Center of Competency - San José
    - 5600 Cottle Road
    - San José, CA 95193
    + others. All Rights Reserved.
    + IBM Globalization Center of Competency - San José
    + 5600 Cottle Road
    + San José, CA 95193
    USA