diff --git a/icu4c/readme.html b/icu4c/readme.html
index c3f79c4472d..52395b8e9bd 100644
--- a/icu4c/readme.html
+++ b/icu4c/readme.html
@@ -1,4 +1,4 @@
-
@@ -44,7 +44,7 @@
This is a release candidate version of ICU4C.
It is not recommended for production use.
- Last updated: 2017-Mar-04
+
Last updated: 2017-Mar-28
Copyright © 2016 and later: Unicode, Inc. and others. License & terms of use:
http://www.unicode.org/copyright.html
Copyright © 1997-2016 International Business Machines Corporation and others.
@@ -235,6 +235,18 @@
+ Important changes
+
+ - All source files are UTF-8 encoded. On platforms where the native charset is not UTF-8,
+ including Windows, check the settings of your editor before working with the source.
+ - Compiler support for C++11 is now required for building the ICU libraries.
+ - The type of UChar is char16_t, on all platforms. This is no longer configurable.
+ This change may affect Windows code with assumptions that UChar was wchar_t, and thus
+ type compatible with other Windows code expecting wchar_t strings.
+ - Windows XP and Windows Vista are no longer supported. (The minimum supported version is Windows 7).
+ - Building the Visual Studio UWP projects requires Visual Studio 2015 Update 3 with a version of the Windows 10 SDK installed.
+
+
API Changes
See the API Change Report for a complete
list of APIs added, removed, or changed in this release.
@@ -246,22 +258,6 @@
For more news about this release, as well as late-breaking news, see the
ICU download page.
- New for 59 RC
-
- - Windows XP and Windows Vista are no longer supported. (The minimum supported version is Windows 7).
- - Building the Visual Studio UWP projects requires Visual Studio 2015 Update 3 with a version of the Windows 10 SDK installed.
-
-
- New for 59 Milestone 1
-
- - Compiler support for C++11 is required for building the ICU libraries.
- - All source files are UTF-8 encoded. On platforms where the native charset is not UTF-8,
- including Windows, check the settings of your editor before working with the source.
- - The type of UChar is char16_t, on all platforms. This is no longer configurable.
- This change may affect Windows code with assumptions that UChar was wchar_t, and thus
- type compatible with other Windows code expecting wchar_t strings.
-
-
@@ -516,12 +512,31 @@
brkitr/ Data files for character, word, sentence, title
casing and line boundary analysis.
+ coll/ Data for collation tailorings. The makefile
+ colfiles.mk contains the list of resource bundle files.
+
locales/ These .txt files contain ICU language and
culture-specific localization data. Two special bundles are
root, which is the fallback data and parent of other bundles,
and index, which contains a list of installed bundles. The
makefile resfiles.mk contains the list of resource bundle
- files.
+ files. Some of the locale data is split out into the type-specific
+ directories curr, lang, region, unit, and zone, described below.
+
+ curr/ Locale data for currency symbols and names (including
+ plural forms), with its own makefile resfiles.mk.
+
+ lang/ Locale data for names of languages, scripts, and locale
+ key names and values, with its own makefile resfiles.mk.
+
+ region/ Locale data for names of regions, with its own
+ makefile resfiles.mk.
+
+ unit/ Locale data for measurement unit patterns and names,
+ with its own makefile resfiles.mk.
+
+ zone/ Locale data for time zone names, with its own
+ makefile resfiles.mk.
mappings/ Here are the code page converter tables. These
.ucm files contain mappings to and from Unicode. These are compiled
@@ -543,9 +558,9 @@
information.
misc/ The misc directory contains other data files which
- did not fit into the above categories. Currently it only contains
- time zone information, and a name preperation file for IDNA.
+ did not fit into the above categories, including time zone
+ information, region-specific data, and other data derived from CLDR
+ supplemental data.
out/ This directory contains the assembled memory mapped
files.
@@ -1677,7 +1692,7 @@ gnumake
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
+ SUn Solaris document available from Oracle. Most notably, pay strict attention to the
following statements from Sun:
@@ -1691,10 +1706,15 @@ gnumake
Failure to do this may cause spurious lock conflicts, recursive mutex
failure, and deadlock.
- Source: "Solaris Multithreaded Programming Guide, Compiling and
- Debugging", Sun Microsystems, Inc., Apr 2004
+
Source: "Multithreaded Programming Guide, Compiling and
+ Debugging", Sun Microsystems, 2002
http://docs.sun.com/app/docs/doc/816-5137/6mba5vpke?a=view
+ "https://docs.oracle.com/cd/E19683-01/806-6867/compile-74765/index.html">https://docs.oracle.com/cd/E19683-01/806-6867/compile-74765/index.html
+
+ Note, a version of that chapter from a 2008 document update covering both Solaris 9
+ and Solaris 10 is available here:
+ http://docs.oracle.com/cd/E19253-01/816-5137/compile-94179/index.html