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-Language" content="en-us"> 7 <meta name="COPYRIGHT" content= "Copyright (c) 1991-2021 Unicode, Inc. All rights reserved."> 8 <meta name="DESCRIPTION" content= "Readme for Unicode CLDR with version number and other information."> 9 <title>ReadMe for Unicode CLDR</title> 10 </head> 11 12 <body> 13 <h2>Unicode Common Locale Data Repository (CLDR)</h2> 14 <h3>ReadMe for Unicode <abbr title="Common Locale Data Repository">CLDR</abbr> version 40</h3> 15 <p>Last updated: 2021-Oct-19</p> 16 17 <!--<p><b>Note:</b> CLDR 40 is in development and not recommended for use at this stage.</p>--> 18 <!--<p><b>Note:</b> This is the milestone 1 version of CLDR 40, intended for those wishing to do pre-release testing. 19 It is not recommended for production use.</p>--> 20 <!--<p><b>Note:</b> This is a preliminary version of CLDR 40, intended for those wishing to do pre-release testing. 21 It is not recommended for production use.</p>--> 22 <!--<p><b>Note:</b> This is a pre-release candidate version of CLDR 40, intended for testing. 23 It is not recommended for production use.</p>--> 24 <p>This is the final release version of CLDR 40.</p> 25 26 <p><strong>Important notes for CLDR 36 and later:</strong></p> 27 <ul> 28 <li>The CLDR repository has switched from subversion to git.</li> 29 <li>Data in the main CLDR repository now includes some elements with the value “↑↑↑” indicating 30 that translators have explicitly determined that the inherited value should always be used.</li> 31 <li>To generate data in the form that was used for CLDR 35.1 and earlier, in which “↑↑↑” is 32 resolved appropriately (either removed or replaced with an apropriate value) and other minimization 33 is performed, a new tool GenerateProductionData is provided (command-line options provide the 34 ability to specify source and destination directory, among other things).</li> 35 <li>CLDR data that has been processed by GenerateProductionData is available in the parallel 36 “cldr-staging” repository.</li> 37 </ul> 38 39 <p>For further information:</p> 40 <ul> 41 <li>Information about <a href="https://cldr.unicode.org/index/downloads">CLDR releases and downloads</a>, 42 including the data files and LDML specification associated with each release.</li> 43 <li>Information about <a href="https://cldr.unicode.org/development/cldr-tools">Building and running CLDR Tools</a></li> 44 </ul> 45 <p>Tools Quickstart:</p> 46 <ul> 47 <li>See the <a href="https://cldr.unicode.org/development/cldr-tools">CLDR Tools Website</a></li> 48 </ul> 49 50 <p>Licenses:</p> 51 <ul> 52 <li>Usage of CLDR data and software is governed by the <a href="http://www.unicode.org/copyright.html">Unicode Terms of Use</a>, 53 a copy of which is included as unicode-license.txt.</li> 54 <li>Some CLDR tools depend on libraries in tools/cldr-code/libs/; use of these libraries is governed by separate license agreements. 55 <ul> 56 <li>Use of the ICU libraries is subject to the 57 <a href="https://github.com/unicode-org/icu/blob/master/icu4j/main/shared/licenses/LICENSE">ICU License</a>, 58 included as ICU-LICENSE.</li> 59 <li>Use of the Guava, Xerces, and Myanmar Tools libraries is subject to the 60 <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License</a>, 61 included as apache-license.txt.</li> 62 </ul> 63 </li> 64 </ul> 65 66 <hr> 67 <p>Copyright © 1991-2021 Unicode, Inc.<br> 68 All rights reserved.<br> 69 <a href="http://www.unicode.org/copyright.html">Terms of use</a></p> 70 </body> 71</html> 72