1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
2   "http://www.w3.org/TR/html4/loose.dtd">
3<html>
4<head>
5  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
6  <meta http-equiv="Content-Style-Type" content="text/css2">
7  <title>ReadMe for ICU4J</title>
8  <meta name="COPYRIGHT" content="Copyright 2000-2015, International Business Machines Corporation and others. All Rights Reserved.">
9  <style type="text/css">
10h3.doc { background: #CCCCFF }
11h4.doc { text-decoration: underline }
12  </style>
13</head>
14<body style="background-color: rgb(255, 255, 255);" lang="EN-US"
15 link="#0000ff" vlink="#800080">
16<h1>International Components for Unicode for Java (ICU4J)</h1>
17<h2>Read Me for ICU4J 56.1</h2>
18(Last Update: 2015-October-06)
19<hr size="2" width="100%">
20
21<p>
22<b>Note:</b> This is major release of ICU4J. It contains bug fixes and adds implementations
23of inherited API and introduces new API or functionality. -->
24<!-- <b>Note:</b> This is a development release of ICU4J 56.
25The contents of this document may not reflect the recent changes done
26for ICU 56 development. This milestone is intended for those wishing
27to get an early look at ICU4J 56 new features and API changes. It is not
28recommended for production use. -->
29<!-- <b>Note:</b> This is a release candidate of ICU4J 56.
30The contents of this document may not reflect the recent changes done
31for ICU 56 development. This release candidate is intended for those
32wishing to verify ICU 56 integration before final release. It is not
33recommended for production use. -->
34<!-- <b>Note:</b> This is a development release of ICU4J 56.
35The contents of this document may not reflect the recent changes done
36for ICU 56 development. This milestone is intended for those
37wishing to verify ICU 56 integration before final release. It is not
38recommended for production use. -->
39</p>
40<p>For the most recent release, see the <a
41 href="http://www.icu-project.org/download/"> ICU4J
42download site</a>. </p>
43<h2 class="doc">Contents</h2>
44<ul type="disc">
45  <li><a href="#introduction">Introduction to ICU4J</a></li>
46  <li><a href="#changes">Changes In This Release</a></li>
47  <li><a href="#license">License Information</a></li>
48  <li><a href="#PlatformDependencies">Platform Dependencies</a></li>
49  <li><a href="#download">How to Download ICU4J</a></li>
50  <li><a href="#WhatContain">The Structure and Contents of ICU4J</a></li>
51  <li><a href="#API">Where to Get Documentation</a></li>
52  <li><a href="#HowToInstallJavac">How to Install and Build</a></li>
53  <li><a href="#HowToModularize">How to modularize ICU4J</a></li>
54  <li><a href="#tryingout">Trying Out ICU4J</a></li>
55  <li><a href="#resources">ICU4J Resource Information</a></li>
56  <li><a href="#timezone">About ICU4J Time Zone</a></li>
57  <li><a href="#WhereToFindMore">Where to Find More Information</a></li>
58  <li><a href="#SubmittingComments">Submitting Comments, Requesting
59Features and Reporting Bugs</a></li>
60</ul>
61<h2 class="doc"><a name="introduction"></a>Introduction to ICU4J</h2>
62<p>The International Components for Unicode (ICU) library provides
63robust and
64full-featured Unicode services on a wide variety of platforms. ICU
65supports the
66most current version of the Unicode standard, including support for
67supplementary characters (needed for GB 18030 repertoire support).</p>
68<p>Java provides a strong foundation for global programs, and IBM and
69the
70ICU team played a key role in providing globalization technology to
71Java. But because of its long release schedule, Java cannot always keep
72up with evolving standards. The ICU team continues to extend Java's
73Unicode and internationalization support, focusing on improving
74performance,
75keeping current with the Unicode standard, and providing richer APIs,
76while
77remaining as compatible as possible with the original Java text and
78internationalization API design.</p>
79<p>ICU4J is an add-on to the regular JRE that provides:
80</p>
81<ul>
82  <li><a
83 href="http://www.icu-project.org/userguide/Collate_Intro.html"><b>Collation</b></a>
84&#8211; rule-based, up-to-date Unicode Collation Algorithm (UCA) sorting order<br>
85&nbsp;&nbsp;&nbsp;&nbsp;For fast multilingual string comparison; faster
86and more complete than
87the J2SE implementation</li>
88  <li><a href="http://www.icu-project.org/userguide/charsetDetection.html"><b>Charset
89Detection</b></a> &#8211; Recognition of various single and multibyte charsets<br>
90&nbsp;&nbsp;&nbsp;&nbsp;Useful for recognizing untagged text data</li>
91  <li><a
92 href="http://www.icu-project.org/userguide/unicodeSet.html"><b>UnicodeSet</b></a>
93&#8211; standard set operations optimized for sets of Unicode characters<br>
94&nbsp;&nbsp;&nbsp;&nbsp;UnicodeSets can be built from string patterns
95using any Unicode properties.</li>
96  <li><a href="http://www.icu-project.org/userguide/Transform.html"><b>Transforms</b></a>
97&#8211; a flexible mechanism for Unicode text conversions<br>
98&nbsp;&nbsp;&nbsp;&nbsp;Including Full/Halfwidth conversions,
99Normalization, Case conversions, Hex
100conversions, and transliterations between scripts (50+ pairs)</li>
101  <li><a
102 href="http://www.icu-project.org/userguide/normalization.html"><b>Unicode
103Normalization</b></a> &#8211; NFC, NFD, NFKD, NFKC<br>
104&nbsp;&nbsp;&nbsp;&nbsp;For canonical text representations, needed for
105XML and the net</li>
106  <li><a
107 href="http://www.icu-project.org/userguide/dateCalendar.html"><b>International
108Calendars</b></a> &#8211; Arabic, Buddhist, Chinese, Hebrew, Japanese, Ethiopic, Islamic, Coptic and other calendars<br>
109&nbsp;&nbsp;&nbsp;&nbsp;Required for correct presentation of dates in
110certain countries</li>
111  <li><a
112 href="http://www.icu-project.org/userguide/formatNumbers.html"><b>Number
113Format
114Enhancements</b></a> &#8211; Scientific Notation, Spelled-out, etc.<br>
115&nbsp;&nbsp;&nbsp;&nbsp;Enhancements to the normal Java number
116formatting. The spell-out format is
117used for checks and similar documents</li>
118  <li><a
119 href="http://www.icu-project.org/userguide/boundaryAnalysis.html"><b>Enhanced
120Word-Break Detection</b></a> &#8211; Rule-based, supports Thai<br>
121&nbsp;&nbsp;&nbsp;&nbsp;Required for correct support of Thai</li>
122  <li><a
123 href="http://www.icu-project.org/userguide/compression.html"><b>Unicode
124Text
125Compression</b></a> &#8211; Standard compression of Unicode text<br>
126&nbsp;&nbsp;&nbsp;&nbsp;Suitable for large numbers of small fields,
127where LZW and similar schemes
128do not apply</li>
129  <li><a
130 href="http://www.icu-project.org/userguide/conversion.html"><b>Charset Conversion</b></a> &#8211; Conversion to and from different charsets.<br>
131&nbsp;&nbsp;&nbsp;&nbsp;Plugs into Java CharsetProvider Service Provider Interface (SPI)</li>
132
133</ul>
134<blockquote>
135  <p><b>Note:</b> We continue to provide assistance to Java, and in some
136cases, ICU4J support has been rolled into a later release of Java. For
137example, BCP47 language tag support including Unicode locale extensions
138is now in Java 7. However, the most current and complete version is always
139found in ICU4J.</p>
140</blockquote>
141
142<h2 class="doc"><a name="changes"></a>Changes In This Release</h2>
143
144<p>See the <a href="https://sites.google.com/site/icusite/download/56">ICU 56 download page</a>
145about new features in this release.
146The list of API changes since the previous ICU4J release is available
147<a href="http://source.icu-project.org/repos/icu/icu4j/tags/release-56-1/APIChangeReport.html">here</a>.</p>
148
149    <!-- ICU 56 items -->
150    <!-- <h3>[Subject]</h3> -->
151
152    <!-- end ICU 56 items -->
153
154<h2 class="doc"><a name="license"></a>License Information</h2>
155<p>
156The ICU projects (ICU4C and ICU4J) use the X license. The X
157license is <b>suitable for commercial use</b> and is a recommended free software license
158that is compatible with the GNU GPL license. This became
159effective with release 1.8.1 of ICU4C and release 1.3.1 of ICU4J in
160mid-2001. All new ICU releases will adopt the X license; previous ICU
161releases continue to utilize the IPL (IBM Public License). Users
162of previous releases of ICU who want to adopt new ICU releases will
163need to accept the terms and conditions of the X license.
164</p>
165<p>
166The main effect of the change is to provide GPL compatibility.
167The X license is listed as GPL compatible, see the GNU page at
168<a href="http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses">
169http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses</a>.
170This means that GPL projects can now use ICU code, it does <b>not</b>
171mean that projects using ICU become subject to GPL.
172</p>
173<p>
174 The IBM version contains the essential text of the license, omitting the
175X-specific trademarks and copyright notices. The full copy of <a
176 href="http://source.icu-project.org/repos/icu/icu4j/tags/release-56-1/main/shared/licenses/license.html">ICU's license</a> is included in the download
177package.
178</p>
179<h2 class="doc"><a name="PlatformDependencies"></a>Platform Dependencies</h2>
180<p>
181ICU4J 56 depends on J2SE 5.0 functionality.  Therefore, ICU4J only runs on
182JRE version 5.0 or later.
183The table below shows the operating systems and JRE/VM versions currently
184used by the ICU development team to test ICU4J.
185</p>
186<table border="1">
187<tr>
188  <th rowspan="2">Operating System</th>
189  <th colspan="2">JRE 8</th>
190  <th colspan="2">JRE 7</th>
191  <th colspan="2">JRE 6</th>
192  <th colspan="2">JRE 5</th>
193</tr>
194<tr>
195  <th>32bit</th>
196  <th>64bit</th>
197  <th>32bit</th>
198  <th>64bit</th>
199  <th>32bit</th>
200  <th>64bit</th>
201  <th>32bit</th>
202  <th>64bit</th>
203</tr>
204<tr>
205  <th>AIX 6.1</th>
206  <td align="center">-</td>
207  <td align="center">-</td>
208  <td align="center">-</td>
209  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
210  <td align="center">-</td>
211  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
212  <td align="center">-</td>
213  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
214</tr>
215<tr>
216  <th>AIX 7.1</th>
217  <td align="center">-</td>
218  <td align="center">-</td>
219  <td align="center">-</td>
220  <td align="center" bgcolor="#CCCCFF"><em><b>Reference platform</b></em></td>
221  <td align="center">-</td>
222  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
223  <td align="center">-</td>
224  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
225</tr>
226<tr>
227  <th>HP-UX 11 (IA64)</th>
228  <td align="center">-</td>
229  <td align="center">-</td>
230  <td align="center">-</td>
231  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
232  <td align="center">-</td>
233  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
234  <td align="center">-</td>
235  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
236</tr>
237<tr>
238  <th>Mac OS X 10.6</th>
239  <td align="center">-</td>
240  <td align="center">-</td>
241  <td align="center">-</td>
242  <td align="center">-</td>
243  <td align="center">-</td>
244  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
245  <td align="center">-</td>
246  <td align="center">-</td>
247</tr>
248<tr>
249  <th>Redhat Enterprise Linux 6 (x86)</th>
250  <td align="center">-</td>
251  <td align="center">-</td>
252  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
253  <td align="center">-</td>
254  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
255  <td align="center">-</td>
256  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
257  <td align="center">-</td>
258</tr>
259<tr>
260  <th>Redhat Enterprise Linux 6 (x86_64)</th>
261  <td align="center">-</td>
262  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
263  <td align="center">-</td>
264  <td align="center" bgcolor="#CCCCFF"><em><b>Reference platform</b></em></td>
265  <td align="center">-</td>
266  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
267  <td align="center">-</td>
268  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
269</tr>
270<tr>
271<th>Solaris 10 (SPARC)</th>
272  <td align="center">-</td>
273  <td align="center">-</td>
274  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
275  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
276  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
277  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
278  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
279  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
280</tr>
281<tr>
282  <th>Solaris 11 (SPARC)</th>
283  <td align="center">-</td>
284  <td align="center">-</td>
285  <td align="center">-</td>
286  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
287  <td align="center">-</td>
288  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
289  <td align="center">-</td>
290  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
291</tr>
292<tr>
293  <th>Windows XP</th>
294  <td align="center">-</td>
295  <td align="center">-</td>
296  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
297  <td align="center">-</td>
298  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
299  <td align="center">-</td>
300  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
301  <td align="center">-</td>
302</tr>
303<tr>
304  <th>Windows Vista</th>
305  <td align="center">-</td>
306  <td align="center">-</td>
307  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
308  <td align="center">-</td>
309  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
310  <td align="center">-</td>
311  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
312  <td align="center">-</td>
313</tr>
314<tr>
315  <th>Windows 7</th>
316  <td align="center">-</td>
317  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
318  <td align="center" bgcolor="#CCCCFF"><em><b>Reference platform</b></em></td>
319  <td align="center">-</td>
320  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
321  <td align="center">-</td>
322  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
323  <td align="center">-</td>
324</tr>
325<tr>
326  <th>Windows 2008 Server</th>
327  <td align="center">-</td>
328  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
329  <td align="center">-</td>
330  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
331  <td align="center">-</td>
332  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
333  <td align="center">-</td>
334  <td align="center" bgcolor="#DDDDFF">Regularly tested</td>
335</tr>
336</table>
337
338<h2 class="doc"><a name="download"></a>How to Download ICU4J</h2>
339<p>There are two ways to download the ICU4J releases.
340</p>
341<ul type="disc">
342  <li><b>Official Release:</b><br>
343If you want to use ICU4J (as opposed to developing it), your best bet
344is to download an official, packaged version of the ICU4J library files.
345These versions are tested more thoroughly than day-to-day development
346builds, and they are packaged in jar files for convenient download.
347These packaged files can be found at the
348<a href="http://www.icu-project.org/download/">ICU Download page</a>.
349</li></ul>
350<ul type="disc">
351  <li><b>Subversion Source Repository:</b><br>
352If you are interested in developing features, patches, or bug fixes for
353ICU4J, you should probably be working with the latest version of the
354ICU4J source code. You will need to check the code out of our Subversion
355repository to ensure that you have the most recent version of all of
356the files. There are several ways to do this. Please follow the
357directions that are contained on the <a
358 href="http://www.icu-project.org/repository/">Source
359 Repository page</a> for details.
360  </li>
361</ul>
362<p>For more details on how to download ICU4J directly from the web
363site, please see the ICU download page at <a
364 href="http://www.icu-project.org/download/">http://www.icu-project.org/download/</a>
365</p>
366<h2 class="doc"><a name="WhatContain"></a>The Structure and Contents of
367ICU4J</h2>
368<p>Below, all directory pathes are relative to the directory where the
369ICU4J source archive is extracted.
370</p>
371<p><b>Information and build files:</b></p>
372<table border="1">
373<tr>
374  <th>Path</th>
375  <th>Description</th>
376</tr>
377<tr>
378  <td>readme.html</td>
379  <td>A description of ICU4J (International Components for Unicode for Java)</td>
380</tr>
381<tr>
382  <td>build.html</td>
383  <td>The main Ant build file for ICU4J.  See <a href="#HowToInstallJavac">How to Install
384  and Build</a> for more information</td>
385</tr>
386<tr>
387  <td>main/shared/licenses/license.html</td>
388  <td>The X license, used by ICU4J</td>
389</tr>
390</table>
391
392<p><b>ICU4J runtime class files:</b></p>
393<table border="1">
394<tr>
395  <th>Path</th>
396  <th>Sub-component Name</th>
397  <th>Build Dependencies</th>
398  <th>Public API Packages</th>
399  <th>Description</th>
400</tr>
401<tr>
402  <td>main/classes/charset</td>
403  <td>icu4j-charset</td>
404  <td>icu4j-core</td>
405  <td>com.ibm.icu.charset</td>
406  <td>Implementation of <code>java.nio.charset.spi.CharsetProvider</code>.
407  This sub-component is shipped as icu4j-charset.jar along with
408  ICU charset converter data files.</td>
409</tr>
410<tr>
411  <td>main/classes/collate</td>
412  <td>icu4j-collate</td>
413  <td>icu4j-core</td>
414  <td>com.ibm.icu.text<br>
415  com.ibm.icu.util</td>
416  <td>Collator APIs and implementation.  Also includes some public API classes
417  that depend on Collator.
418  This sub-component is packaged as a part of icu4j.jar.</td>
419</tr>
420<tr>
421  <td>main/classes/core</td>
422  <td>icu4j-core</td>
423  <td>n/a</td>
424  <td>com.ibm.icu.lang<br>
425  com.ibm.icu.math<br>
426  com.ibm.icu.text<br>
427  com.ibm.icu.util</td>
428  <td>ICU core API classes and implementation.
429  This sub-component is packaged as a part of icu4j.jar.</td>
430</tr>
431<tr>
432  <td>main/classes/currdata</td>
433  <td>icu4j-currdata</td>
434  <td>icu4j-core</td>
435  <td>n/a</td>
436  <td>No public API classes.  Provides access to currency display data.
437  This sub-component is packaged as a part of icu4j.jar.</td>
438</tr>
439<tr>
440  <td>main/classes/langdata</td>
441  <td>icu4j-langdata</td>
442  <td>icu4j-core</td>
443  <td>n/a</td>
444  <td>No public API classes.  Provides access to language display data.
445  This sub-component is packaged as a part of icu4j.jar.</td>
446</tr>
447<tr>
448  <td>main/classes/localespi</td>
449  <td>icu4j-localespi</td>
450  <td>icu4j-core<br>
451  icu4j-collate<br>
452  </td>
453  <td>n/a</td>
454  <td>Implementation of various locale-sensitive service providers defined
455  in <code>java.text.spi</code> and <code>java.util.spi</code> in J2SE 6.0
456  or later Java releases.
457  This sub-component is shipped as icu4j-localespi.jar.</td>
458</tr>
459<tr>
460  <td>main/classes/regiondata</td>
461  <td>icu4j-regiondata</td>
462  <td>icu4j-core</td>
463  <td>n/a</td>
464  <td>No public API classes.  Provides access to region display data.
465  This sub-component is packaged as a part of icu4j.jar.</td>
466</tr>
467<tr>
468  <td>main/classes/translit</td>
469  <td>icu4j-translit</td>
470  <td>icu4j-core</td>
471  <td>com.ibm.icu.text</td>
472  <td>Transliterator APIs and implementation.
473  This sub-component is packaged as a part of icu4j.jar.</td>
474</tr>
475</table>
476
477<p><b>ICU4J unit test files:</b></p>
478<table border="1">
479<tr>
480  <th>Path</th>
481  <th>Sub-component Name</th>
482  <th>Runtime Dependencies</th>
483  <th>Description</th>
484</tr>
485<tr>
486  <td>main/tests/charset</td>
487  <td>icu4j-charset-tests</td>
488  <td>icu4j-charset<br>
489  icu4j-core<br>
490  icu4j-test-framework</td>
491  <td>Test suite for charset sub-component.</td>
492</tr>
493<tr>
494  <td>main/tests/collate</td>
495  <td>icu4j-collate-tests</td>
496  <td>icu4j-collate<br>
497  icu4j-core<br>
498  icu4j-test-framework</td>
499  <td>Test suite for collate sub-component.</td>
500</tr>
501<tr>
502  <td>main/tests/core</td>
503  <td>icu4j-core-tests</td>
504  <td>icu4j-core<br>
505  icu4j-currdata<br>
506  icu4j-langdata<br>
507  icu4j-regiondata<br>
508  icu4j-test-framework</td>
509  <td>Test suite for core sub-component.</td>
510</tr>
511<tr>
512  <td>main/tests/framework</td>
513  <td>icu4j-test-framework</td>
514  <td>icu4j-core</td>
515  <td>Common ICU4J unit test framework and utilities.</td>
516</tr>
517<tr>
518  <td>main/tests/localespi</td>
519  <td>icu4j-localespi-tests</td>
520  <td>icu4j-core<br>
521  icu4j-collate<br>
522  icu4j-currdata<br>
523  icu4j-langdata<br>
524  icu4j-localespi<br>
525  icu4j-regiondata<br>
526  icu4j-test-framework</td>
527  <td>Test suite for localespi sub-component.</td>
528</tr>
529<tr>
530  <td>main/tests/packaging</td>
531  <td>icu4j-packaging-tests</td>
532  <td>icu4j-core<br>
533  icu4j-test-framework</td>
534  <td>Test suite for sub-component packaging.</td>
535</tr>
536<tr>
537  <td>main/tests/translit</td>
538  <td>icu4j-translit-tests</td>
539  <td>icu4j-core<br>
540  icu4j-translit
541  icu4j-test-framework</td>
542  <td>Test suite for translit sub-component.</td>
543</tr>
544</table>
545
546<p><b>Others:</b></p>
547<table border="1">
548<tr>
549  <th>Path</th>
550  <th>Description</th>
551</tr>
552<tr>
553  <td>main/shared</td>
554  <td>Files shared by ICU4J sub-components under the <code>main</code> directory including:
555  <ul>
556    <li>ICU4J runtime data archive (icudata.jar).</li>
557    <li>ICU4J unit test data archive (testdata.jar).</li>
558    <li>Shared Ant build script and configuration files.</li>
559    <li>License files.</li>
560  </ul>
561  </td>
562</tr>
563<tr>
564  <td>demos</td>
565  <td>ICU4J demo programs.</td>
566</tr>
567<tr>
568  <td>perf-tests</td>
569  <td>ICU4J performance test files.</td>
570</tr>
571<tr>
572  <td>tools</td>
573  <td>ICU4J tools including:
574  <ul>
575    <li>Custom JavaDoc taglets used for generating ICU4J API references.</li>
576    <li>API report tool and data.</li>
577    <li>Other independent utilities used for ICU4J development.</li>
578  </ul>
579  </td>
580</tr>
581</table>
582
583<h2 class="doc"><a name="API"></a>Where to get Documentation</h2>
584<p>The <a href="http://www.icu-project.org/userguide/">ICU user's
585guide</a> contains lots of general information about ICU, in its C,
586C++, and Java incarnations.</p>
587<p>The complete API documentation for ICU4J (javadoc) is available on
588the ICU4J web site, and can be built from the sources:
589</p>
590<ul>
591  <li><a href="http://www.icu-project.org/apiref/icu4j/">Index
592to all ICU4J API</a></li>
593  <li><a href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/text/CharsetDetector.html">Charset Detector</a> &#8211; Detection of charset from a byte stream</li>
594  <li>International Calendars &#8211;
595    <a
596 href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/util/BuddhistCalendar.html">Buddhist</a>,
597    <a
598 href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/util/ChineseCalendar.html">Chinese</a>,
599    <a
600 href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/util/CopticCalendar.html">Coptic</a>,
601    <a
602 href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/util/EthiopicCalendar.html">Ethiopic</a>,
603    <a
604 href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/util/GregorianCalendar.html">Gregorian</a>,
605    <a
606 href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/util/HebrewCalendar.html">Hebrew</a>,
607    <a
608 href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/util/IndianCalendar.html">Indian</a>,
609    <a
610 href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/util/IslamicCalendar.html">Islamic</a>,
611    <a
612 href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/util/JapaneseCalendar.html">Japanese</a>,
613    Persian, Dangi.</li>
614  <li>Time Zone Enhancements &#8211;
615<a href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/util/BasicTimeZone.html">Time zone transition and rule detection</a>,
616<a href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/util/VTimeZone.html">iCalendar VTIMEZONE formatting and parsing</a>,
617<a href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/util/RuleBasedTimeZone.html">Custom time zones constructed by user defined rules</a>.
618  <li>Date Format Enhancements &#8211; <a href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/text/DateTimePatternGenerator.html">Date/Time Pattern Generator</a>,
619<a href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/text/DateIntervalFormat.html">Date Interval Format</a>,
620<a href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/text/DurationFormat.html">Duration Format</a>.
621  <li><a
622 href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/text/Normalizer.html">Unicode
623Normalization</a> &#8211; Canonical text representation for W3C.</li>
624  <li><a
625 href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/text/NumberFormat.html">Number
626Format Enhancements</a> &#8211; Scientific Notation, Spelled out.</li>
627  <li><a
628 href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/text/BreakIterator.html">Enhanced
629word-break detection</a> &#8211; Rule-based, supports Thai</li>
630  <li><a
631 href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/text/Transliterator.html">Transliteration</a>
632&#8211; A general framework for converting text from one format to another,
633e.g. Cyrillic to Latin, or Hex to Unicode. </li>
634  <li>Unicode Text <a
635 href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/text/UnicodeCompressor.html">Compression</a>
636&amp; <a
637 href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/text/UnicodeDecompressor.html">Decompression</a>
638&#8211; 2:1 compression on English Unicode text.</li>
639  <li>Collation &#8211; <a
640 href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/text/RuleBasedCollator.html">Rule-based
641sorting</a>, <a
642 href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/text/StringSearch.html">Efficient
643multi-lingual searching</a>,
644<a href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/text/AlphabeticIndex.html">Alphabetic indexing</a></li>
645</ul>
646<h2 class="doc"><a name="HowToInstallJavac"></a>How to Install and Build</h2>
647<p>
648To install ICU4J, simply place the prebuilt jar file <strong>icu4j.jar</strong>
649on your Java CLASSPATH. If you need Charset API support please also place
650<strong>icu4j-charset.jar</strong> on your class path along with <strong>icu4j.jar</strong>.
651</p>
652<p>
653To build ICU4J, you will need J2SE SDK 5.0 or later (ICU4J locale SPI
654provider sub-components require J2SE SDK 6.0 or later) and the Ant build system
655version 1.7 or later. It's recommended to install both the J2SE SDK and Ant
656somewhere <em>outside</em>the ICU4J directory. For example, on Linux you might install
657these in <code>/usr/local</code>.</p>
658<ul>
659  <li>Install J2SE SDK 7.</li>
660  <li>Install the <a href="http://ant.apache.org/"><strong>Ant</strong></a>
661  build system. Ant is a portable, Java-based build system similar to
662  make. ICU4J uses Ant because it introduces no other dependencies, it's
663  portable, and it's easier to manage than a collection of makefiles. We
664  currently build ICU4J using a single makefile on all platforms Ant.
665  The build system requires Ant 1.7 or later.
666    <p>Installing Ant is straightforward. Download it (see <a
667 href="http://ant.apache.org/bindownload.cgi">http://ant.apache.org/bindownload.cgi</a>),
668extract it onto your system, set some environment variables, and add
669its bin directory to your path. For example: </p>
670    <pre>
671        set JAVA_HOME=C:\jdk1.7.0
672        set ANT_HOME=C:\ant
673        set PATH=%JAVA_HOME%\bin;%ANT_HOME%\bin;%PATH%</pre>
674    <p>See the current Ant documentation for details.</p>
675  </li>
676</ul>
677<p>Once the J2SE SDK and Ant are installed, building is just a matter of
678typing <strong>ant</strong> in the ICU4J root directory. This causes the
679Ant build system to perform the build target <strong>jar</strong>
680as specified by the file <strong>build.xml</strong>, located in the ICU4J
681root directory. You can give Ant options like -verbose, and you can specify
682other targets.  For example:</p>
683<blockquote>
684<pre>C:\icu4j>ant
685Buildfile: C:\icu4j\build.xml
686
687info:
688     [echo] ----- Build Environment Information -------------------
689     [echo] Java Home:    C:\jdk1.7.0\jre
690     [echo] Java Version: 1.7.0
691     [echo] Ant Home:     C:\ant
692     [echo] Ant Version:  Apache Ant(TM) version 1.9.4 compiled on April 29 2014
693     [echo] OS:           Windows 7
694     [echo] OS Version:   6.1
695     [echo] OS Arch:      amd64
696     [echo] Host:         ICUDEV
697     [echo] -------------------------------------------------------
698
699core:
700
701@compile:
702     [echo] build-local:     ../../shared/../../build-local.properties
703     [echo] ${java5.bootclasspath}
704     [echo] --- java compiler arguments ------------------------
705     [echo] source dir:     C:\icu4j\main\classes\core/src
706     [echo] output dir:     C:\icu4j\main\classes\core/out/bin
707     [echo] bootclasspath:
708     [echo] classpath:
709     [echo] source:         1.5
710     [echo] target:         1.5
711     [echo] debug:          on
712     [echo] encoding:       UTF-8
713     [echo] compiler arg:   -Xlint:all,-deprecation,-dep-ann,-options
714     [echo] ----------------------------------------------------
715    [mkdir] Created dir: C:\icu4j\main\classes\core\out\bin
716    [javac] Compiling 365 source files to C:\icu4j\main\classes\core\out\bin
717    [javac] Note: Some input files use or override a deprecated API.
718    [javac] Note: Recompile with -Xlint:deprecation for details.
719
720compile:
721
722@copy:
723     [copy] Copying 23 files to C:\icu4j\main\classes\core\out\bin
724
725set-icuconfig-datapath:
726
727copy-data:
728    [unjar] Expanding: C:\icu4j\main\shared\data\icudata.jar into C:\icu4j\main\
729classes\core\out\bin
730    [unjar] Expanding: C:\icu4j\main\shared\data\icutzdata.jar into C:\icu4j\mai
731n\classes\core\out\bin
732
733...
734...
735...
736
737_build-localespi:
738
739@compile:
740     [echo] build-local:     ../../shared/../../build-local.properties
741     [echo] ${java5.bootclasspath}
742     [echo] --- java compiler arguments ------------------------
743     [echo] source dir:     C:\icu4j\main\classes\localespi/src
744     [echo] output dir:     C:\icu4j\main\classes\localespi/out/bin
745     [echo] classpath:      C:\icu4j\main\classes\core\out\lib\icu4j-core.jar;C:
746\icu4j\main\classes\collate\out\lib\icu4j-collate.jar
747     [echo] source:         1.6
748     [echo] target:         1.6
749     [echo] debug:          on
750     [echo] encoding:       UTF-8
751     [echo] compiler arg:   -Xlint:all,-deprecation,-dep-ann,-options
752     [echo] ----------------------------------------------------
753    [mkdir] Created dir: C:\icu4j\main\classes\localespi\out\bin
754    [javac] Compiling 22 source files to C:\icu4j\main\classes\localespi\out\bin
755
756
757compile:
758
759@copy:
760     [copy] Copying 10 files to C:\icu4j\main\classes\localespi\out\bin
761
762copy:
763
764@jar:
765    [mkdir] Created dir: C:\icu4j\main\classes\localespi\out\lib
766     [copy] Copying 1 file to C:\icu4j\main\classes\localespi\out
767      [jar] Building jar: C:\icu4j\main\classes\localespi\out\lib\icu4j-localesp
768i.jar
769
770jar:
771
772@src-jar:
773      [jar] Building jar: C:\icu4j\main\classes\localespi\out\lib\icu4j-localesp
774i-src.jar
775
776src-jar:
777
778build:
779
780jar:
781     [copy] Copying 1 file to C:\icu4j
782     [copy] Copying 1 file to C:\icu4j
783
784BUILD SUCCESSFUL
785Total time: 50 seconds</pre>
786</blockquote>
787<I>Note: The above output is an example. The numbers are likely to be different with the current version ICU4J.</I>
788<p>The following are some targets that you can provide to <b>ant</b>.
789For more targets run <code>ant -projecthelp</code> or see the build.xml file.</p>
790<table border="1">
791<tr>
792  <th>jar (default)</th>
793  <td>Create ICU4J runtime library jar archives (<code>icu4j.jar</code>,
794  <code>icu4j-charset.jar</code> and <code>icu4j-localespi.jar</code>)
795  in the root ICU4J directory.</td>
796</tr>
797<tr>
798  <th>check</th>
799  <td>Build all ICU4J runtime library classes and corresponding unit test cases,
800  then run the tests.</td>
801</tr>
802<tr>
803  <th>clean</th>
804  <td>Remove all build output files.</td>
805</tr>
806<tr>
807  <th>main</th>
808  <td>Build all ICU4J runtime library sub-components (under the directory
809  <code>main/classes</code>).</td>
810</tr>
811<tr>
812  <th>tests</th>
813  <td>Build all ICU4J unit test sub-components (under the directory <code>main/tests</code>)
814  and their dependencies.</td>
815</tr>
816<tr>
817  <th>tools</th>
818  <td>Build the tools.</td>
819</tr>
820<tr>
821  <th>docs</th>
822  <td>Run javadoc over the ICU4J runtime library files, generating an HTML documentation
823  tree in the subdirectory <code>doc</code>.</td>
824</tr>
825<tr>
826  <th>jarDocs</th>
827  <td>Create ICU4J doc jar archive (<code>icu4jdocs.jar</code>) containing API reference
828  docs in the root ICU4J directory. </td>
829</tr>
830<tr>
831  <th>jarDemos</th>
832  <td>Create ICU4J demo jar archive (<code>icu4jdemos.jar</code>) in the root ICU4J
833  directory.</td>
834</tr>
835</table>
836
837<p>For more information, read the Ant documentation and the <strong>build.xml</strong>
838file.</p>
839<p><b>Note:</b> If you get an OutOfMemoryError when you are running <tt>"ant check"</tt>,
840you can set the heap size of the jvm by setting the environment variable JVM_OPTIONS
841to the appropriate java options.</p>
842
843<p><b>Eclipse users:</b> See the ICU4J site for information on<a
844 href="http://www.icu-project.org/docs/eclipse_howto/eclipse_howto.html">
845how to configure Eclipse</a> to build and develop ICU4J on Eclipse IDE.</p>
846
847<p><b>Note:</b> To install and configure ICU4J Locale Service Provider, please refer the user guide
848page <a href="http://userguide.icu-project.org/icu4j-locale-service-provider">ICU4J Locale
849Service Provider</a>.</p>
850
851<!--  <p><b>Note:</b> ICU4J 56 does not support JDK 8 javadoc tool yet. The build targets "doc" and
852"docs" will fail when JDK 8 javadoc tool is used.</p>  -->
853
854<h2 class="doc"><a name="HowToModularize"></a>How to modularize ICU4J</h2>
855<p>Some clients may not wish to ship all of ICU4J with their
856application, since the application might only use a small part of ICU4J.
857ICU4J release 2.6 and later provide build options to build individual
858ICU4J 'modules' for a more compact distribution.  For more details, please
859refer to the section <em>Modularization of ICU4J</em> in the ICU user's
860guide article <a href="http://userguide.icu-project.org/packaging-icu4j">Packaging ICU4J</a>.
861
862<h2 class="doc"><a name="tryingout"></a>Trying Out ICU4J</h2>
863<p><strong>Note:</strong> the demos provided with ICU4J are for the
864most part undocumented. This list can show you where to look, but
865you'll have to experiment a bit. The demos are <strong>unsupported</strong>
866and may change or disappear without notice.</p>
867<p>The icu4j.jar file contains only the ICU4J runtime library classes, not the
868demo classes, so unless you build ICU4J there is little to try out.
869</p>
870<h3>Charset</h3>
871To try out the <strong>Charset</strong> package, build <strong>icu4j.jar</strong> and
872<strong>icu4j-charset.jar</strong> using the 'jar' target.
873You can use the charsets by placing these files on your classpath.
874<blockquote><tt>java -cp $icu4j_root/icu4j.jar:$icu4j_root/icu4j-charset.jar &lt;your program&gt;</tt></blockquote>
875<h3>Other demos</h3>
876<p>The other demo programs are <strong>not supported</strong> and
877exist only to let you experiment with the ICU4J classes. First, build ICU4J using <tt>ant&nbsp;jarDemos</tt>.
878Then launch the demos as below:</p>
879<blockquote><tt>java -jar $icu4j_root/icu4jdemos.jar</tt></blockquote>
880
881<h2 class="doc"><a name="resources">ICU4J Resource Information</a></h2>
882Starting with release 2.1, ICU4J includes its own
883resource information
884which is completely independent of the JRE resource information. (Note,
885ICU4J 2.8 to 3.4, time zone information depends on the underlying JRE).
886The ICU4J resource information is equivalent to the information in ICU4C and
887many resources are, in fact, the same binary files that ICU4C uses.
888<p>
889By default the ICU4J distribution includes all of the standard resource
890information. It is located under the directory com/ibm/icu/impl/data.
891Depending on the service, the data is in different locations and in
892different formats. <strong>Note:</strong> This will continue to change
893from release to release, so clients should not depend on the exact
894organization
895of the data in ICU4J.</p>
896<ul>
897  <li>The primary <b>locale data</b> is under the directory <tt>icudt56b</tt>,
898  as a set of <tt>".res"</tt> files whose names are the locale identifiers.
899  Locale naming is documented the <code>com.ibm.icu.util.ULocale</code>
900  class, and the use of these names in searching for resources is documented
901  in <code>com.ibm.icu.util.UResourceBundle</code>.</li>
902
903  <li>The <b>break iterator data</b> is under the directory <tt>icudt56b/brkitr</tt>,
904  as a set of <tt>".res"</tt>, <tt>".brk"</tt> and <tt>".dict"</tt> files.</li>
905
906  <li>The <b>collation data</b> is under the directory <tt>icudt56b/coll</tt>,
907  as a set of <tt>".res"</tt> files.</li>
908
909  <li>The <b>currency display name data</b> is under the directory <tt>icudt56b/curr</tt>,
910  as a set of <tt>".res"</tt> files.</li>
911
912  <li>The <b>language display name data</b> is under the directory <tt>icudt56b/lang</tt>,
913  as a set of <tt>".res"</tt> files.</li>
914
915  <li>The <b>rule-based number format data</b> is under the directory
916  <tt>icudt56b/rbnf</tt>, as a set of <tt>".res"</tt> files.
917
918  <li>The <b>region display name data</b> is under the directory <tt>icudt56b/region</tt>,
919  as a set of <tt>".res"</tt> files.</li>
920
921  <li>The <b>rule-based transliterator data</b> is under the directory
922  <tt>icudt56b/translit</tt>, as a set of <tt>".res"</tt> files.</li>
923
924  <li>The <b>measurement unit data</b> is under the directory <tt>icudt56b/unit</tt>,
925  as a set of <tt>".res"</tt> files.</li>
926
927  <li>The <b>time zone display name data</b> is under the directory
928  <tt>icudt56b/zone</tt>, as a set of <tt>".res"</tt> files.</li>
929
930  <li>The <b>character property data</b> and default <b>unicode collation algorithm
931  (UCA) data</b> is found under the directory <tt>icudt56b</tt>, as a set of
932  <tt>".icu"</tt> files. </li>
933
934  <li>The <b>normalization data</b> is found under the directory <tt>icudt56b</tt>,
935  as a set of <tt>".nrm"</tt> files. </li>
936
937  <li>The <b>character set converter data</b> is under the directory
938  <tt>icudt56b</tt>, as a set of <tt>".cnv"</tt> files.  These files are
939  currently included only in icu-charset.jar.</li>
940
941  <li>The <b>time zone rule data</b> is under the directory
942  <tt>icudt56b</tt>, as <tt>zoneinfo64.res</tt>.</li>
943
944  <li>The <b>holiday data</b> is under the directory <tt>icudt56b</tt>,
945  as a set of <tt>".class"</tt> files, named <tt>"HolidayBundle_"</tt>
946  followed by the locale ID.</li>
947
948</ul>
949<p>
950Some of the data files alias or otherwise reference data from other
951data files. One reason for this is because some locale names have
952changed. For example, <tt>he_IL</tt> used to be <tt>iw_IL</tt>. In
953order to support both names but not duplicate the data, one of the
954resource files refers to the other file's data. In other cases, a
955file may alias a portion of another file's data in order to save
956space. Currently ICU4J provides no tool for revealing these
957dependencies.</p>
958<blockquote><strong>Note:</strong>  Java's <code>Locale</code> class
959silently converts the language code <tt>"he"</tt> to <tt>"iw"</tt>
960when you construct the Locale (for versions of Java through Java 5). Thus
961Java cannot be used to locate resources that use the <tt>"he"</tt>
962language code. ICU, on the other hand, does not perform this
963conversion in ULocale, and instead uses aliasing in the locale data to
964represent the same set of data under different locale
965ids.</blockquote>
966<p>
967Resource files that use locale ids form a hierarchy, with up to four
968levels: a root, language, region (country), and variant. Searches for
969locale data attempt to match as far down the hierarchy as possible,
970for example, <tt>"he_IL"</tt> will match <tt>he_IL</tt>, but
971<tt>"he_US"</tt> will match <tt>he</tt> (since there is no <tt>US</tt>
972variant for he, and <tt>"xx_YY</tt> will match root (the
973default fallback locale) since there is no <tt>xx</tt> language code
974in the locale hierarchy. Again, see
975<code>java.util.ResourceBundle</code> for more information.
976</p>
977<p>
978<strong>Currently ICU4J provides no tool for revealing these
979dependencies</strong> between data files, so trimming the data
980directly in the ICU4J project is a hit-or-miss affair. The key point
981when you remove data is to make sure to remove all dependencies on
982that data as well. For example, if you remove <tt>he.res</tt>, you
983need to remove <tt>he_IL.res</tt>, since it is lower in the hierarchy,
984and you must remove iw.res, since it references <tt>he.res</tt>, and
985<tt>iw_IL.res</tt>, since it depends on it (and also references
986<tt>he_IL.res</tt>).
987</p>
988<p>
989Unfortunately, the jar tool in the JDK provides no way to remove items
990from a jar file. Thus you have to extract the resources, remove the
991ones you don't want, and then create a new jar file with the remining
992resources. See the jar tool information for how to do this. Before
993'rejaring' the files, be sure to thoroughly test your application with
994the remaining resources, making sure each required resource is
995present.
996</p>
997<h3>Using additional resource files with ICU4J</h3>
998<blockquote>
999  <table cellpadding="3" frame="border" rules="none" width="50%">
1000    <tbody>
1001      <tr>
1002        <td><b><font color="red" size="+1">Warning:</font> Resource
1003file formats can change across releases of ICU4J!</b></td>
1004      </tr>
1005      <tr>
1006        <td>The format of ICU4J resources is not part of the API.
1007Clients who develop their own resources for use with ICU4J should be
1008prepared to
1009regenerate them when they move to new releases of ICU4J.</td>
1010      </tr>
1011    </tbody>
1012  </table>
1013</blockquote>
1014<p>
1015We are still developing ICU4J's resource mechanism. Currently it
1016is not possible to mix icu's new binary <tt>.res</tt>
1017resources
1018with traditional java-style <tt>.class</tt> or <tt>.txt</tt>
1019resources. We might
1020allow for this in a future release, but since the resource data and
1021format is not formally
1022supported, you run the risk of incompatibilities with future releases
1023of ICU4J.
1024</p>
1025<p>
1026Resource data in ICU4J is checked in to the repository as a jar file
1027containing the resource binaries, <tt>$icu4j_root/main/shared/data/icudata.jar</tt>.
1028This means that inspecting the contents of these resources is difficult.
1029They currently are compiled from ICU4C <tt>.txt</tt> file data. You
1030can view the contents of the ICU4C text resource files to understand
1031the contents of the ICU4J resources.
1032</p>
1033<p>
1034The files in <tt>icudata.jar</tt> get extracted to <tt>com/ibm/icu/impl/data</tt>
1035in the build output directory by some build targets.
1036</p>
1037<h3><a name="resourcesICU4C">Building ICU4J Resources from ICU4C</a></h3>
1038ICU4J data is built by ICU4C tools. Please see "icu4j-readme.txt" in <I>$icu4c_root</I>/source/data for the procedures.
1039<h5> Generating Data from CLDR </h5>
1040<I> Note: This procedure assumes that all 3 sources are present</I>
1041<ol>
1042    <li>Checkout or download CLDR version 'release-28'</li>
1043    <li>Checkout ICU4C with tag 'release-56-1'</li>
1044    <li>Checkout ICU4J with tag 'release-56-1'</li>
1045    <li>cd to <I>$icu4c_root</I>/source/data directory</li>
1046    <li>Follow the instructions in <I>$icu4c_root</I>/source/data/cldr-icu-readme.txt</li>
1047    <li>Rebuild ICU4C with the newly generated data.</li>
1048    <li>Run ICU4C tests to verify that the new data is good.</li>
1049    <li>Build ICU4J data from ICU4C data by following the procedures in <I>$icu4c_root</I>/source/data/icu4j-readme.txt</li>
1050    <li>cd to <I>$icu4j_root</I> dir</li>
1051
1052    <li>Build and test icu4j</li>
1053</ol>
1054
1055<h2 class="doc"><a name="timezone"></a>About ICU4J Time Zone</h2>
1056<p>ICU4J 56 Release Candidate includes time zone data version 2015f, which is the latest one as of
1057the release date. However, time zone data is frequently updated in response
1058to changes made by local governments around the world.  If you need to update
1059the time zone data, please refer the ICU user guide topic
1060<a href="http://userguide.icu-project.org/datetime/timezone#TOC-Updating-the-Time-Zone-Data">Updating the Time Zone Data</a>.</p>
1061<p>Starting with ICU4J 4.0, you can optionally configure ICU4J date and time
1062service classes to use underlying JDK TimeZone implementation (see the ICU4J API reference
1063<a href="http://www.icu-project.org/apiref/icu4j/com/ibm/icu/util/TimeZone.html">TimeZone</a>
1064for the details).  When this configuration is enabled, ICU's own time zone data
1065won't be used and you have to get time zone data patches from the JRE vendor.</p>
1066
1067<h2 class="doc"><a name="WhereToFindMore"></a>Where to Find More
1068Information</h2>
1069<p><a href="http://www.icu-project.org/">http://www.icu-project.org/</a>
1070is the home page of International Components for Unicode development project</p>
1071<p><a href="http://www.ibm.com/software/globalization/icu/">http://www.ibm.com/software/globalization/icu/</a>
1072is a pointer to general information about the International Components for
1073Unicode hosted by IBM</p>
1074<p><a href="http://www.ibm.com/software/globalization/">http://www.ibm.com/software/globalization/</a>
1075is a pointer to
1076information on how to make applications global. </p>
1077<h2 class="doc"><a name="SubmittingComments"></a>Submitting Comments,
1078Requesting Features and
1079Reporting Bugs</h2>
1080<p>Your comments are important to making ICU4J successful. We are
1081committed to investigate any bug reports or suggestions,
1082and will use your feedback to help plan future releases.</p>
1083<p>To submit comments, request features and report bugs,
1084please see <a href="http://www.icu-project.org/bugs.html">ICU bug database
1085information</a> or contact us through the <a
1086 href="http://www.icu-project.org/contacts.html">ICU Support
1087mailing list</a>.  While we are not able to respond individually to each comment, we do
1088review all comments.</p>
1089<br>
1090<br>
1091<h2>Thank you for your interest in ICU4J!</h2>
1092<br>
1093<hr align="center" size="2" width="100%">
1094<p><I><font size="-1">Copyright &copy; 2000-2015 International Business
1095Machines Corporation and others. All Rights
1096Reserved.<br>
10974400 North First Street, San Jos&eacute;, CA 95193, USA
1098</font></I></p>
1099</body>
1100</html>
1101