1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 2<html> 3<head> 4 5 6 7<meta http-equiv="Content-Language" content="en-us"> 8 9 10 11<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> 12 13 14 15<link rel="stylesheet" type="text/css" 16 href="http://unicode.org/cldr/apps/surveytool.css"> 17 18 19 20 21 22<title>Help Text file for Survey tool</title> 23<style> 24<!-- 25DIV.chat { 26 PADDING-RIGHT: 2px; 27 PADDING-LEFT: 2px; 28 PADDING-BOTTOM: 4px; 29 PADDING-TOP: 4px 30} 31 32DIV.in { 33 HEIGHT: 1px; 34 TEXT-ALIGN: left 35} 36 37DIV.1st { 38 PADDING-TOP: 4px 39} 40--> 41</style> 42</head> 43 44 45<body> 46 47 48 49 <h1 align="center">Survey Tool Help Text</h1> 50 51 52 <p> 53 This is a help-text file for use with the survey tool. You can add a 54 new row, where the <i>Path</i> is a regular expression for an XML 55 path, and the <i>Text to Insert</i> is what you want to show up as 56 help text, or modify existing text. <b>The software that 57 interprets this expects a particular format, so don't make arbitrary 58 changes (see the end). </b> 59 </p> 60 61 62 <table id="table1" style="border-collapse: collapse;" border="1" 63 bordercolor="#000080" cellspacing="0" width="100%"> 64 65 66 <tbody> 67 68 <tr> 69 70 71 <th>Path</th> 72 73 74 <th>Text to Insert</th> 75 76 77 </tr> 78 79 80 <tr> 81 82 83 <td>//ldml/localeDisplayNames.*</td> 84 85 86 <td> 87 88 89 <h3>Display Names</h3> 90 91 92 93 94 <p> 95 Languages, scripts (writing systems), territories (countries and 96 regions), currencies, and time zones are represented in computers 97 by internal codes, such as " 98 <code>fr</code> 99 " for the French language or " 100 <code>CA</code> 101 " for the country of Canada. 102 </p> 103 104 105 106 107 <p> 108 <i>The ISO names and the "official" names are often not the 109 best ones for CLDR.</i> The goal is the most customary name used in 110 your language, even if it is not the official name. For example, 111 for the territory name in English you would use "Switzerland" 112 instead of "Swiss Confederation", and use "United Kingdom" instead 113 of "The United Kingdom of Great Britain and Northern Ireland". The 114 best source for customary usage is to look at what common 115 publications such as newspapers and magazines do. For example, to 116 see how Congo is used in French, one might search <a 117 target="_blank" 118 onClick="return top.js.OpenExtLink(window,event,this)" 119 href="http://www.google.com/search?q=Congo+site%3Alemonde.fr"> 120 http://www.google.com/search?q<wbr>=Congo+site%3Alemonde.fr 121 </a> and other publications. 122 </p> 123 124 125 126 127 <p> 128 All names <b>must</b> be unique within a given category: thus one 129 cannot use the same translated name for the following two codes; <i>only 130 one can be called "Congo":</i> 131 </p> 132 133 134 135 136 <table style="border-collapse: collapse;" id="table3" border="1" 137 bordercolor="#009900" cellspacing="0"> 138 139 140 <tbody> 141 142 <tr> 143 144 145 <th style="vertical-align: top; text-align: left;">Code</th> 146 147 148 <th style="vertical-align: top; text-align: left;" colspan="5">Possible 149 Pairs of Translations</th> 150 151 152 </tr> 153 154 155 <tr> 156 157 158 <td style="text-align: center; vertical-align: top;"><code>CD</code></td> 159 160 161 <td style="vertical-align: top; text-align: left;"><i>Democratic 162 Republic of the Congo</i></td> 163 164 165 <td style="vertical-align: top; text-align: left;" rowspan="2">or</td> 166 167 168 <td style="vertical-align: top; text-align: left;"><i>Congo 169 - Kinshasa</i></td> 170 171 172 <td style="vertical-align: top; text-align: left;" rowspan="2">or</td> 173 174 175 <td style="vertical-align: top; text-align: left;"><i>Congo 176 - formerly Zaire</i></td> 177 178 179 </tr> 180 181 182 <tr> 183 184 185 <td style="text-align: center; vertical-align: top;"><code>CG</code></td> 186 187 188 <td style="vertical-align: top; text-align: left;"><i>Congo</i></td> 189 190 191 <td style="vertical-align: top; text-align: left;"><i>Congo 192 - Brazzaville</i></td> 193 194 195 <td style="vertical-align: top; text-align: left;"><i>Congo</i></td> 196 197 198 </tr> 199 200 201 202 203 </tbody> 204 205 </table> 206 207 208 209 210 <p>Avoid using commas and avoid inverting the name (eg "Congo, 211 Democratic Republic of the"). The characters "(" and ")" are 212 discouraged, since they will be confusing in combination with 213 countries in locale names.</p> 214 215 </td> 216 217 218 </tr> 219 220 221 <tr> 222 223 224 <td>//ldml/localeDisplayNames/(keys|types).*</td> 225 226 227 <td> 228 229 230 <h3 align="left">Keys</h3> 231 232 233 234 235 <p align="left"> 236 The <strong style="font-weight: 400;">keys</strong> page lists the 237 key names for translation. These identify particular key words 238 used to identify particular <i>types</i> of variants. The calendar 239 types are typically only used with certain languages, however, 240 they can be used with almost any language: 241 </p> 242 243 244 245 246 <table style="border-collapse: collapse;" id="table4" border="1" 247 bordercolor="#009900" cellspacing="0"> 248 249 250 <tbody> 251 252 <tr> 253 254 255 <th style="vertical-align: top; text-align: left;">Locale 256 Code</th> 257 258 259 <th style="vertical-align: top; text-align: left;">Locale 260 Name (English)</th> 261 262 263 </tr> 264 265 266 <tr> 267 268 269 <td style="vertical-align: top;"><code>fr@calendar=buddhist</code></td> 270 271 272 <td style="vertical-align: top; text-align: left;">French 273 (Buddhist Calendar)</td> 274 275 276 </tr> 277 278 279 <tr> 280 281 282 <td style="vertical-align: top;"><code>de@calendar=buddhist</code></td> 283 284 285 <td style="vertical-align: top; text-align: left;">German 286 (Buddhist Calendar)</td> 287 288 289 </tr> 290 291 292 <tr> 293 294 295 <td style="vertical-align: top;"><code>...</code></td> 296 297 298 <td style="vertical-align: top; text-align: left;">...</td> 299 300 301 </tr> 302 303 304 305 306 </tbody> 307 308 </table> 309 310 311 312 313 <p>The collation (sort order) types, on the other hand, are 314 only used with certain locales (listed below):</p> 315 316 317 318 319 <table style="border-collapse: collapse;" id="table5" border="1" 320 bordercolor="#009900" cellspacing="0"> 321 322 323 <tbody> 324 325 <tr> 326 327 328 <th style="vertical-align: top; text-align: left;">Locale 329 Code</th> 330 331 332 <th style="vertical-align: top; text-align: left;">Locale 333 Name (English)</th> 334 335 336 </tr> 337 338 339 <tr> 340 341 342 <td style="vertical-align: top;"><code>de@collation=phonebook</code></td> 343 344 345 <td style="vertical-align: top; text-align: left;">German 346 (Phonebook Sort Order)</td> 347 348 349 </tr> 350 351 352 <tr> 353 354 355 <td style="vertical-align: top;"><code>hi@collation=direct</code></td> 356 357 358 <td style="vertical-align: top; text-align: left;">Hindi 359 (Direct Sort Order)</td> 360 361 362 </tr> 363 364 365 <tr> 366 367 368 <td style="vertical-align: top;"><code>zh@collation=pinyin</code></td> 369 370 371 <td style="vertical-align: top; text-align: left;">Chinese 372 (Pinyin Sort Order)</td> 373 374 375 </tr> 376 377 378 <tr> 379 380 381 <td style="vertical-align: top;"><code>zh@collation=stroke</code></td> 382 383 384 <td style="vertical-align: top; text-align: left;">Chinese 385 (Stroke Sort Order)</td> 386 387 388 </tr> 389 390 391 <tr> 392 393 394 <td style="vertical-align: top;"><code>zh@collation=gb2312han</code></td> 395 396 397 <td style="vertical-align: top; text-align: left;">Chinese 398 (Simplified Sort Order - GB2312)</td> 399 400 401 </tr> 402 403 404 <tr> 405 406 407 <td style="vertical-align: top;"><code>zh@collation=big5han</code></td> 408 409 410 <td style="vertical-align: top; text-align: left;">Chinese 411 (Traditional Sort Order - Big5)</td> 412 413 414 </tr> 415 416 417 <tr> 418 419 420 <td style="vertical-align: top;"><code>es@collation=traditional</code></td> 421 422 423 <td style="vertical-align: top; text-align: left;">Spanish 424 (Traditional Sort Order)</td> 425 426 427 </tr> 428 429 430 431 432 </tbody> 433 434 </table> 435 436 437 438 439 <p align="left"> 440 The last value ( 441 <code>traditional</code> 442 ) is the only one likely to be extended to other languages over 443 time. 444 </p> 445 446 447 </td> 448 449 450 </tr> 451 452 453 <tr> 454 455 456 <td>//ldml/localeDisplayNames/territories.*</td> 457 458 459 <td> 460 461 462 <h3>Territories</h3> 463 464 465 466 467 <p> 468 Territories include both country names and regions: continents and 469 subcontinents (defined by a UN standard). All of these must be 470 unique: for example, you can't give the same name to the country <i>South 471 Africa</i> (the country) and to <i>Southern Africa</i> (the southern 472 region of the continent of Africa), even though there may be no 473 distinction in your language between the terms for "<i>South</i>" 474 and "<i>Southern</i>". Similarly, <i>North America</i> is the 475 continent that extends down to Panama; <i>Northern America</i> is 476 the region of the Americas north of Mexico. 477 </p> 478 479 480 481 482 <p> 483 The country name should be the most natural; you may have to 484 adjust the name of the region. So you might say the equivalent of 485 "South Region of Africa", or add clarifying language like "<span 486 class="loser"><i>Amérique du Nord continentale</i>" vs "<i>Amérique 487 du Nord</i>". If you have any question as to the extent of any 488 region, see <a target="_blank" 489 href="http://www.unicode.org/cldr/data/charts/supplemental/territory_containment_un_m_49.html">Territory 490 Containment</a>. </span> 491 </p> 492 493 494 495 496 <ul> 497 498 499 <li>A common question is whether to capitalize or not. With a 500 new locale, use whatever is normal practice for what should occur 501 in <b>menus</b>. For an existing locale, <i>especially during 502 the vetting period,</i> follow what is used for the other items 503 already translated. 504 505 <ul> 506 507 508 <li><i>If the capitalization convention as a whole for 509 a language needs to be changed, that should be done before the 510 data submission phase for the next release. Please file a bug 511 to request that this be done.</i></li> 512 513 514 515 516 </ul> 517 518 519 </li> 520 521 522 </ul> 523 524 </td> 525 526 527 </tr> 528 529 530 <tr> 531 532 533 <td>//ldml/localeDisplayNames/languages.*</td> 534 535 536 <td> 537 538 539 <h3>Languages</h3> 540 541 542 543 544 <p> 545 There are a lot of languages here (around 500), and you <em>don't</em> 546 need to look at them all! Many are relatively obscure, and not 547 worth translating in a first pass. Please also look at the 548 following points. 549 </p> 550 551 552 553 554 <ul> 555 556 557 <li>Please use phrasing corresponding to the English "Baltic 558 Language" for language collections. That is, use terms that would 559 be appropriate to use for indicating that the target text is "a" 560 Baltic Language, without terms that imply exclusion or 561 multiplicity such as "other" (autre), etc. or "languages" 562 (plural).</li> 563 564 565 <li>A common question is whether to capitalize or not. With a 566 new locale, use whatever is normal practice for what should occur 567 in <b>menus</b>. For an existing locale, <i>especially during 568 the vetting period,</i> follow what is used for the other items 569 already translated. This is the practice for scripts, territories 570 and other types of items too. 571 572 <ul> 573 574 575 <li><i>If the capitalization convention as a whole for 576 a language needs to be changed, that should be done before the 577 data submission phase for the next release. Please file a bug 578 to request that this be done.</i></li> 579 580 581 582 583 </ul> 584 585 586 </li> 587 588 589 590 591 </ul> 592 593 594 </td> 595 596 597 </tr> 598 599 600 <tr> 601 602 603 <td>//ldml/localeDisplayNames/languages.*\[@type="[^"]*_[^"]*"\].*</td> 604 605 606 <td> 607 608 609 <h3>Compound Language Codes</h3> 610 611 612 613 614 <p> 615 Some language codes are more complex, of the form "en_AU" for <i>Australian 616 English</i>. If you don't add a translation, then those will be 617 represented by a format like "αγγλικά (Αυστραλία)". That is, the 618 translation would be the native name for "English", followed by 619 the native word for "Australia" in parentheses. If that format is 620 ok, then you don't need to translate the more complex language 621 code. The codes zh_Hant and zh_Hans (for Traditional and 622 Simplified Chinese) on the other hand, should always be 623 translated. 624 </p> 625 626 627 628 629 <p>There are a few special cases:</p> 630 631 632 633 634 <ul> 635 636 637 <li>"Iberian Portuguese" is the style of Portuguese used in 638 Portugal (as opposed to Brazil)</li> 639 640 641 <li>Similarly "Iberian Spanish" is the style of Spanish used 642 in Spain (as opposed to Latin America).</li> 643 644 645 <li>"Swiss High German" (<i>Schweizer Hochdeutsch</i>), also 646 called "Swiss Standard German", has the code <code>de_CH</code>. 647 </li> 648 649 650 <li>"Swiss German" (<i>Schwyzerdütsch</i>) has the code <code>gsw</code>. 651 </li> 652 653 654 655 656 </ul> 657 658 659 <p>A pattern is used to control how the translations for 660 language and region codes are composed into a name when the 661 compound code doesn't have a specific translation. See the section 662 "localeDisplayPattern".</p> 663 664 665 </td> 666 667 668 </tr> 669 670 671 <tr> 672 673 674 <td>//ldml/localeDisplayNames/scripts.*</td> 675 676 677 <td> 678 679 680 <h3>Scripts</h3> 681 682 683 684 685 <p>Normally only a few scripts are really necessary to 686 translate: those that are used in distinguishing the most common 687 languages that are written in multiple ways. These are Hant and 688 Hans (for traditional and simplified Chinese), Cyrillic, Arabic, 689 and Latin.</p> 690 691 692 693 694 <ul> 695 696 697 <li>A common question is whether to capitalize or not. With a 698 new locale, use whatever is normal practice for what should occur 699 in <b>menus</b>. For an existing locale, <i>especially during 700 the vetting period,</i> follow what is used for the other items 701 already translated. 702 703 <ul> 704 705 706 <li><i>If the capitalization convention as a whole for 707 a language needs to be changed, that should be done before the 708 data submission phase for the next release. Please file a bug 709 to request that this be done.</i></li> 710 711 712 713 714 </ul> 715 716 717 </li> 718 719 720 </ul> 721 722 </td> 723 724 725 </tr> 726 727 728 <tr> 729 730 731 <td>.*/currencies.*</td> 732 733 734 <td> 735 736 737 <h3>Currencies</h3> 738 739 740 741 742 <p>This is a long list that contains the currency names and 743 currency symbols for each country, plus historical codes. The 744 coverage level option tries to pick out the ones that are most 745 important to translate. Each currency code can be translated in 746 two ways:</p> 747 748 749 750 751 <ul> 752 753 754 <li>As a symbol for use in formatting amounts (such as "12 755 345,68 <b>US$</b>"), and 756 </li> 757 758 759 <li>As a name, typically used to show a list of currencies 760 (such as "<b>dollar des États-Unis</b>") 761 </li> 762 763 764 <li>With names, the common question of whether to capitalize 765 or not, arises. With the introduction of pluralized units in CLDR 766 1.6, it is recognized that currency names may be used equally in 767 menus and flowing text. Therefore, for a new locale, use whatever 768 practice is best suited for use in either <b>menus</b> or <b>flowing 769 text</b> <i>(we recognize that the capitalization rule you adopt 770 may have limitations, and we endeavour to add additional 771 features to the Survey Tool, in the future to alleviate some of 772 these limitations )</i>. For an existing locale, <i>especially 773 during the vetting period,</i> follow what is used for the other 774 items already translated. 775 </li> 776 777 778 </ul> 779 780 781 </td> 782 783 784 </tr> 785 786 787 <tr> 788 789 790 <td>//ldml/characters/exemplarCharacters.*</td> 791 792 793 <td> 794 795 796 <h3>Exemplar Character Set</h3> 797 798 799 800 801 <p> 802 The exemplar character sets contain the commonly used letters for 803 a given modern form of a language. These are used for testing and 804 for determining the appropriate repertoire of letters for charset 805 conversion or text comparison. The term "letter" is interpreted 806 broadly, and includes characters used to form words, such as 是 or 807 가. If a sequence of characters is considered a "letter", it will 808 be listed between { and }. For example, <em>{ch}</em>. 809 </p> 810 811 812 813 814 <p>There are three categories:</p> 815 816 817 818 819 <ul> 820 821 822 <li>The <i>standard</i> characters are those used in 823 customary writing, such as [a-z] for English. 824 </li> 825 826 827 <li>The <i>auxiliary</i> characters are additional characters 828 used in foreign words found in typical magazines, newspapers, 829 &c. For example, you could see the name Schröder in English 830 in a magazine, so <i>ö</i> is in the set. However, it is very 831 uncommon to see <i>ł</i>, so that isn't in the auxiliary set for 832 English. Publication style guides, such as <i>The Economist 833 Style Guide</i> for English, are useful for this. 834 </li> 835 836 837 <li>The <i>currency</i> characters are additional characters 838 used in currency symbols, like 'US$ 1,234'. 839 </li> 840 <li>The <em>index</em> characters are used as an index for 841 categories of items. Unlike the other characters, it should have 842 either uppercase or lowercase, depending on what is typical for 843 the language. Note that if the character set is large without 844 fixed standard sorting (such as Chinese), the value [] should be 845 used.<em class="draft"> A draft set of characters was 846 mechanically generated, and will need adjustments: for example, 847 characters or strings that never occur at the start of words are 848 typically removed.</em></li> 849 850 851 852 853 </ul> The exemplar set is not a complete set of letters used for a 854 language: punctuation and other symbols are not included, nor 855 uppercase letters (except for Turkish İ). The Survey Tool will flag 856 certain fields with <img 857 alt="The image “http://unicode.org/cldr/apps/warn.png” cannot be displayed, because it contains errors." 858 src="http://unicode.org/cldr/apps/warn.png"> if they use 859 characters that are not in exemplar sets. In some cases, this is 860 not truly an error, such as where "NaN" is used in numbers. In 861 other cases, the possible actions for you are are: 862 863 <ul> 864 865 866 <li>Fix the field value to not use the character.</li> 867 868 869 <li>Fix the exemplar sets, because the character actually is 870 acceptable in your language in one of the above categories.</li> 871 872 873 874 875 </ul> 876 877 878 879 880 <p align="left"> 881 Any range of characters, such as "a b c d e" can be represented 882 compactly as "a-e". For more information, please see <i> <a 883 target="_blank" 884 href="http://unicode.org/reports/tr35/tr35-6.html#Character_Elements">Section 885 5.6 Character Elements</a></i> in <i>UTS#35: Locale Data Markup 886 Language (LDML)</i>. 887 </p> 888 889 890 </td> 891 892 893 </tr> 894 895 896 <tr> 897 898 899 <td>.*/numbers.*</td> 900 901 902 <td> 903 904 905 <h3>Numbers</h3> 906 907 908 909 910 <p> 911 Numbers are formatted using patterns, like "#,###.00". Different 912 characters stand for different parts of the number: they don't 913 have their normal meaning!<span style="font-style: italic;"> 914 In particular, you need to use '.' for the decimal point and ',' 915 for the thousands (grouping) separator, even if they are not used 916 that way in your language. </span>Here are the special characters used 917 in number patterns. 918 </p> 919 920 921 922 923 <table style="border-collapse: collapse;" id="table2" border="1" 924 bordercolor="#009900" cellspacing="0"> 925 926 927 <caption> 928 <b>Number Format Symbols</b> 929 </caption> 930 <tbody> 931 932 <tr> 933 934 935 <th style="vertical-align: top; text-align: left;">Symbol</th> 936 937 938 <th style="vertical-align: top; text-align: left;">Meaning</th> 939 940 941 </tr> 942 943 944 <tr> 945 946 947 <td style="text-align: center; vertical-align: top;">.</td> 948 949 950 <td style="vertical-align: top; text-align: left;"><b>Not 951 a real period:</b> instead, it will be replaced automatically by 952 the character used for the decimal point in your language, 953 listed under <tt class="hangsml" title="#194, w[N]:194">symbols/decimal</tt></td> 954 955 956 </tr> 957 958 959 <tr> 960 961 962 <td style="text-align: center; vertical-align: top;">,</td> 963 964 965 <td style="vertical-align: top; text-align: left;"><b>Not 966 a real comma:</b> instead, it will be replaced by the "grouping" 967 (thousands) separator in your language, listed under <tt 968 class="hangsml" title="#4, w[N]:4">symbols/group</tt></td> 969 970 971 </tr> 972 973 974 <tr> 975 976 977 <td style="text-align: center; vertical-align: top;">0</td> 978 979 980 <td style="vertical-align: top; text-align: left;">Replaced 981 by a digit (or zero if there aren't enough digits).</td> 982 983 984 </tr> 985 986 987 <tr> 988 989 990 <td style="text-align: center; vertical-align: top;">#</td> 991 992 993 <td style="vertical-align: top; text-align: left;">Replaced 994 by a digit (or nothing if there aren't enough). Often used to 995 show the position of the ",".</td> 996 997 998 </tr> 999 1000 1001 <tr> 1002 1003 1004 <td style="text-align: center; vertical-align: top;">¤</td> 1005 1006 1007 <td style="vertical-align: top; text-align: left;">This 1008 will be replaced by a currency symbol, such as $ or USD. Note: 1009 by default a space is placed between letters in a currency 1010 symbol and adjacent numbers. If this is not right for your 1011 language, file a bug to change it using the Feedback link.</td> 1012 1013 1014 </tr> 1015 1016 1017 <tr> 1018 1019 1020 <td style="text-align: center; vertical-align: top;">...;...</td> 1021 1022 1023 <td style="vertical-align: top; text-align: left;">If your 1024 language uses different formats for negative numbers than just 1025 adding "-" at the front, you can put in <span 1026 style="font-style: italic;">two</span> patterns. For example: 1027 #,##0.00¤;(#,##0.00¤) is used to make negative currencies 1028 appear like "(<font face="Times New Roman">1'234,56£)" 1029 instead of "-1'234,56£"</font> 1030 </td> 1031 1032 1033 </tr> 1034 1035 1036 1037 1038 </tbody> 1039 1040 </table> 1041 1042 1043 1044 1045 <p align="left">For example, the pattern "#,###.00" when used 1046 to format the number 12345.678 could result in "12'345,67". That 1047 would happen if the grouping separator for your language is an 1048 apostrophe, and the decimal separator is a comma. Translators 1049 should not change the pattern of zeros (0) or hash marks (#); 1050 those will be reset by software. This is true also for currency 1051 formats. Even if your currency doesn't use any decimal points, the 1052 currency format will have them in the pattern. You need to modify 1053 the patterns when:</p> 1054 1055 1056 1057 1058 <ul> 1059 1060 1061 <li>The grouping separator is not by thousands (eg Hindi).</li> 1062 1063 1064 <li>The negative pattern doesn't simply add a minus sign. For 1065 example, if a negative number is formed by adding parentheses, 1066 then this would look like: #,##0.###;(#,##0.###). That is, the 1067 negative form gets added after a semicolon.</li> 1068 1069 1070 <li>The currency symbol (¤) is used in a different position.</li> 1071 1072 1073 1074 1075 </ul> 1076 1077 1078 </td> 1079 1080 1081 </tr> 1082 1083 1084 <tr> 1085 1086 1087 <td>//ldml/dates/calendars/.*/(pattern|dateFormatItem|intervalFormats).*</td> 1088 1089 1090 <td> 1091 1092 1093 <h3>Formats for Dates and Times</h3> 1094 1095 1096 1097 1098 <p>Dates and times are formatted using patterns, like "mm-dd". 1099 Each field, like the month or the hour, is represented by a 1100 sequence of letters from A to Z. For example, one or more M's 1101 stand for the month. When the software formats a date for your 1102 language, a value will be substituted for each field, according to 1103 the following table.</p> 1104 1105 1106 1107 1108 <table style="border-collapse: collapse;" border="1" 1109 bordercolor="#009900" cellspacing="0"> 1110 1111 1112 <caption> 1113 <b>Date Format Symbols</b> 1114 </caption> 1115 <tbody> 1116 1117 <tr> 1118 1119 1120 <th style="vertical-align: top; text-align: left;">Symbol</th> 1121 1122 1123 <th style="vertical-align: top; text-align: left;">Meaning</th> 1124 1125 1126 </tr> 1127 1128 1129 <tr> 1130 1131 1132 <td style="text-align: center; vertical-align: top;">G</td> 1133 1134 1135 <td style="vertical-align: top; text-align: left;">era (eg 1136 AD)*</td> 1137 1138 1139 </tr> 1140 1141 1142 <tr> 1143 1144 1145 <td style="text-align: center; vertical-align: top;">y</td> 1146 1147 1148 <td style="vertical-align: top; text-align: left;">year</td> 1149 1150 1151 </tr> 1152 1153 1154 <tr> 1155 1156 1157 <td style="text-align: center; vertical-align: top;">M / L</td> 1158 1159 1160 <td style="vertical-align: top; text-align: left;">month*</td> 1161 1162 1163 </tr> 1164 1165 1166 <tr> 1167 1168 1169 <td style="text-align: center; vertical-align: top;">E</td> 1170 1171 1172 <td style="vertical-align: top; text-align: left;">day of 1173 the week (eg Tuesday).*</td> 1174 1175 1176 </tr> 1177 1178 1179 <tr> 1180 1181 1182 <td style="text-align: center; vertical-align: top;">d</td> 1183 1184 1185 <td style="vertical-align: top; text-align: left;">day</td> 1186 1187 1188 </tr> 1189 1190 1191 <tr> 1192 1193 1194 <td style="text-align: center; vertical-align: top;">h / H</td> 1195 1196 1197 <td style="vertical-align: top; text-align: left;">hour. h 1198 for 12 hour, H for 24.</td> 1199 1200 1201 </tr> 1202 1203 1204 <tr> 1205 1206 1207 <td style="text-align: center; vertical-align: top;">m</td> 1208 1209 1210 <td style="vertical-align: top; text-align: left;">minute</td> 1211 1212 1213 </tr> 1214 1215 1216 <tr> 1217 1218 1219 <td style="text-align: center; vertical-align: top;">s</td> 1220 1221 1222 <td style="vertical-align: top; text-align: left;">second</td> 1223 1224 1225 </tr> 1226 1227 1228 <tr> 1229 1230 1231 <td style="text-align: center; vertical-align: top;">a</td> 1232 1233 1234 <td style="vertical-align: top; text-align: left;">am/pm. 1235 Only used with "h".</td> 1236 1237 1238 </tr> 1239 1240 1241 <tr> 1242 1243 1244 <td style="text-align: center; vertical-align: top;">z / v</td> 1245 1246 1247 <td style="vertical-align: top; text-align: left;">time 1248 zone. Use v for full format dates, z for long format dates</td> 1249 1250 1251 </tr> 1252 1253 1254 <tr> 1255 1256 1257 <td style="text-align: center; vertical-align: top;">'a'</td> 1258 1259 1260 <td style="vertical-align: top; text-align: left;">since 1261 letters have special meaning, if you want a real letter, you 1262 need to put it in single quotes. For a real single quote, use 1263 '' (that is, two adjacent ' characters).</td> 1264 1265 1266 </tr> 1267 1268 1269 <tr> 1270 1271 1272 <td style="text-align: center; vertical-align: top;" colspan="2"> 1273 1274 1275 <p style="text-align: left;">* Some fields use M or MM for 1276 numeric (eg, 1 or 01); MMM for abbreviated (eg, Sept); and 1277 MMMM for full (eg, September)</p> 1278 1279 1280 </td> 1281 1282 1283 </tr> 1284 1285 1286 1287 1288 </tbody> 1289 1290 </table> <br> 1291 1292 </td> 1293 1294 1295 </tr> 1296 1297 1298 <tr> 1299 1300 <td>//ldml/dates/calendars/.*/intervalFormats.*</td> 1301 1302 <td> 1303 1304 <h3>Interval Formats</h3> 1305 1306 1307 <p>Interval formats are used for a range of dates or times 1308 specified by a start and end, such as "Sept 10-12" (meaning the 1309 10th of September through the 12th of September). The pattern will 1310 be something like "MMM d–d", where some of the fields are repeated 1311 -- typically with some kind of punctuation mark separating the two 1312 fields, but some fields in the second part are omitted. The way 1313 this pattern is used is that the part up to the first repeated 1314 field is formatted with the first date, and the remainder is 1315 formatted with the second date. For example:</p> 1316 1317 1318 1319 1320 <table style="border-collapse: collapse;" id="table7" border="1" 1321 bordercolor="#009900" cellspacing="0"> 1322 1323 1324 <caption> 1325 <b>Interval Formatting</b> 1326 </caption> 1327 <tbody> 1328 1329 <tr> 1330 1331 1332 <th style="vertical-align: top;"><strong>Format 1333 String</strong></th> 1334 1335 1336 <th style="text-align: center;"><strong>Date 1</strong></th> 1337 1338 1339 <th style="text-align: center;"><strong>Date 2</strong></th> 1340 1341 <th>Result</th> 1342 1343 1344 </tr> 1345 1346 1347 <tr> 1348 1349 1350 <td align="center">MMM d–d</td> 1351 1352 1353 <td align="center">2008-09-13</td> 1354 1355 1356 <td align="center">2008-09-15</td> 1357 1358 <td style="text-align: center;">Sept. 13–15</td> 1359 1360 1361 </tr> 1362 1363 1364 <tr> 1365 1366 1367 <td align="center">MMMM–MMMM, yyyy</td> 1368 1369 1370 <td align="center">2008-09-01</td> 1371 1372 1373 <td align="center">2008-11-31</td> 1374 1375 <td style="text-align: center;">September-November, 2008</td> 1376 1377 1378 </tr> 1379 1380 1381 1382 1383 1384 </tbody> 1385 1386 </table> 1387 1388 1389 1390 1391 <p>Each combination of fields can be used with dates that 1392 differ by different amounts. For example, a format for the fields 1393 "yMMMd" (year, abbreviated month, and day) could be used with two 1394 dates that differ by year, month, or day -- each type of 1395 difference might need a different pattern. For example:</p> 1396 1397 1398 1399 1400 <table style="border-collapse: collapse;" id="table7" border="1" 1401 bordercolor="#009900" cellspacing="0"> 1402 1403 1404 <caption> 1405 <b>Greatest Difference</b> 1406 </caption> 1407 <tbody> 1408 1409 <tr> 1410 1411 1412 1413 <th style="text-align: center;"><strong>Date 1</strong></th> 1414 1415 1416 <th style="text-align: center;"><strong>Date 2</strong></th> 1417 1418 <th>Greatest Difference</th> 1419 1420 <th>Format String</th> 1421 1422 <th>Shares</th> 1423 1424 1425 </tr> 1426 1427 1428 <tr> 1429 1430 1431 1432 <td align="center">2008-09-13</td> 1433 1434 1435 <td align="center"><span style="font-weight: bold;">2009</span>-09-15</td> 1436 1437 <td style="text-align: center;">year</td> 1438 1439 <td style="text-align: center;">MMM d, yyyy – MMM d, yyyy</td> 1440 1441 <td style="text-align: center; font-style: italic;">nothing</td> 1442 1443 1444 </tr> 1445 1446 1447 <tr> 1448 1449 1450 1451 <td align="center">2008-09-01</td> 1452 1453 1454 <td align="center">2008-<span style="font-weight: bold;">11</span>-31 1455 </td> 1456 1457 <td style="text-align: center;">month</td> 1458 1459 <td style="text-align: center;">MMM d – MMM d, yyyy</td> 1460 1461 <td style="text-align: center; font-style: italic;">year</td> 1462 1463 1464 </tr> 1465 1466 <tr> 1467 1468 <td align="center">2008-09-01</td> 1469 1470 <td align="center">2008-09-<span style="font-weight: bold;">05</span></td> 1471 1472 <td style="text-align: center;">day</td> 1473 1474 <td style="text-align: center;">MMM d–d, yyyy</td> 1475 1476 <td style="text-align: center; font-style: italic;">year 1477 and month</td> 1478 1479 </tr> 1480 1481 1482 1483 1484 1485 </tbody> 1486 1487 </table> <br> Look carefully at each of the examples to see the kinds 1488 of formats that would be used in your language. 1489 </td> 1490 1491 </tr> 1492 1493 <tr> 1494 1495 <td>//ldml/dates/calendars/.*Context.*</td> 1496 1497 <td> 1498 1499 <h3>Stand-Alone vs. Format Styles</h3> 1500 1501 1502 <p align="left"> 1503 Some languages use two different forms of strings (<i>stand-alone</i> 1504 and <i>format</i>) depending on the context. Typically the <i>stand-alone</i> 1505 version is the nominative form of the word, and the <i>format</i> 1506 version is in the genitive. 1507 </p> 1508 1509 1510 1511 1512 <p align="left"> 1513 Make sure that the correct forms are provided, especially for the 1514 months, and used in the patterns. That is, suppose that the 1515 language uses "Dezembro" for December when standing alone, but 1516 "Dezembru" when with a date (meaning the nth day <em>of</em> that 1517 month). Then the formats for months could be something like: 1518 </p> 1519 1520 1521 1522 1523 <table style="border-collapse: collapse;" id="table7" border="1" 1524 bordercolor="#009900" cellspacing="0"> 1525 1526 1527 <caption> 1528 <b>Stand-Alone vs Format Months</b> 1529 </caption> 1530 <tbody> 1531 1532 <tr> 1533 1534 1535 <th style="vertical-align: top;"><strong>Format 1536 String</strong></th> 1537 1538 1539 <td align="center"><strong>Example1</strong></td> 1540 1541 1542 <td align="center"><strong>Example2</strong></td> 1543 1544 1545 </tr> 1546 1547 1548 <tr> 1549 1550 1551 <td align="center">LLL</td> 1552 1553 1554 <td align="center">Dezembro</td> 1555 1556 1557 <td align="center">Dez.</td> 1558 1559 1560 </tr> 1561 1562 1563 <tr> 1564 1565 1566 <td align="center">d MMM</td> 1567 1568 1569 <td align="center">1 Dezembru</td> 1570 1571 1572 <td align="center">1 Dez.</td> 1573 1574 1575 </tr> 1576 1577 1578 <tr> 1579 1580 1581 <td align="center">MMM d yy</td> 1582 1583 1584 <td align="center">Dezembru 1 1953</td> 1585 1586 1587 <td align="center">1 Dez. 53</td> 1588 1589 1590 </tr> 1591 1592 1593 1594 1595 </tbody> 1596 1597 </table> 1598 1599 1600 1601 1602 <p align="left">Similarly, suppose that your language formats 1603 months differently if they have vowels, eg "14 de gener de 2008" 1604 but "14 d'abril de 2008". In that case, the stand-alone and format 1605 versions of the months should be:</p> 1606 1607 1608 <table style="border-collapse: collapse;" id="table7" border="1" 1609 bordercolor="#009900" cellspacing="0"> 1610 1611 1612 1613 <tbody> 1614 1615 <tr> 1616 1617 1618 1619 <td align="center"><strong>Format Month</strong></td> 1620 1621 1622 <td><span style="font-weight: bold;">Stand-Alone 1623 Month</span></td> 1624 1625 1626 </tr> 1627 1628 1629 <tr> 1630 1631 1632 1633 <td align="center">de gener</td> 1634 1635 1636 <td>gener</td> 1637 1638 1639 </tr> 1640 1641 1642 <tr> 1643 1644 1645 1646 <td align="center">d'abril</td> 1647 1648 1649 <td>abril</td> 1650 1651 1652 </tr> 1653 1654 1655 1656 1657 1658 </tbody> 1659 1660 </table> 1661 1662 1663 1664 1665 <p align="left">These must be coordinated with the format 1666 strings, which can't have the extra "de" before the month:</p> 1667 1668 1669 <table style="border-collapse: collapse;" id="table7" border="1" 1670 bordercolor="#009900" cellspacing="0"> 1671 1672 1673 1674 <tbody> 1675 1676 <tr> 1677 1678 1679 <th style="vertical-align: top;"><strong>Format 1680 String</strong></th> 1681 1682 1683 1684 <th>Date</th> 1685 1686 <td align="center"><strong>Result</strong></td> 1687 1688 1689 </tr> 1690 1691 1692 <tr> 1693 1694 1695 <td colspan="1" rowspan="2" align="center">LLL</td> 1696 1697 1698 1699 <td>2008-1-14</td> 1700 1701 <td align="center">gener</td> 1702 1703 1704 </tr> 1705 1706 1707 <tr> 1708 1709 1710 1711 1712 <td>2008-4-14</td> 1713 1714 <td align="center">abril</td> 1715 1716 1717 </tr> 1718 1719 1720 <tr> 1721 1722 1723 <td colspan="1" rowspan="2" align="center">d MMM 'de' yyyy</td> 1724 1725 1726 1727 <td>2008-1-14</td> 1728 1729 <td align="center">14 d'abril de 2008</td> 1730 1731 1732 </tr> 1733 1734 <tr> 1735 1736 <td>2008-4-14</td> 1737 1738 <td>14 de gener de 2008</td> 1739 1740 </tr> 1741 1742 1743 1744 1745 </tbody> 1746 1747 </table> 1748 1749 1750 1751 1752 <p align="left"> 1753 That is, if your language uses two different forms, then make sure 1754 that there are two forms of the months or days where necessary, <i>and</i> 1755 adjust the date patterns to use the LLL or LLLL stand-alone form 1756 or MMM and MMMM format forms, as needed. 1757 </p> 1758 1759 </td> 1760 1761 </tr> 1762 1763 <tr> 1764 1765 1766 <td>//ldml/dates/calendars/calendar.*timeFormatLength</td> 1767 1768 1769 <td> 1770 1771 1772 <h3>Standard Time Formats</h3> 1773 1774 1775 1776 1777 <p>There are four standard time formats.</p> 1778 1779 1780 1781 1782 <ul> 1783 1784 1785 <li>full should contain hour, minute, second, and long zone 1786 (vvvv).</li> 1787 1788 1789 <li>long should contain hour, minute, second, and zone (z)</li> 1790 1791 1792 <li>medium should contain hour, minute, second.</li> 1793 1794 1795 <li>short should contain hour, minute.</li> 1796 1797 1798 1799 1800 </ul> 1801 1802 1803 </td> 1804 1805 1806 </tr> 1807 1808 1809 <tr> 1810 1811 1812 <td>//ldml/dates/calendars/calendar.*/quarters/.*</td> 1813 1814 1815 <td> 1816 1817 1818 <h3>Quarters</h3> 1819 1820 1821 1822 1823 <p>The quarters of a year are used in formats such as "2006Q3", 1824 typically used for financial periods. If your language doesn't 1825 have a common term for this, you might use the equivalent of 1826 "Jan-Mar".</p> 1827 1828 1829 </td> 1830 1831 1832 </tr> 1833 1834 1835 <tr> 1836 1837 1838 <td>//ldml/dates/calendars/calendar.*/fields.*displayName.*</td> 1839 1840 1841 <td> 1842 1843 1844 <h3>Date Field Labels</h3> 1845 1846 1847 1848 1849 <p>The date field labels are the names of the dates or time 1850 field, such as "Month" or "Hour", suitable for labels in dialogs 1851 or menus.</p> 1852 1853 1854 </td> 1855 1856 1857 </tr> 1858 1859 1860 <tr> 1861 1862 1863 <td>//ldml/dates/calendars/calendar.*/fields.*relative.*</td> 1864 1865 1866 <td> 1867 1868 1869 <h3>Relative Periods of Time</h3> 1870 1871 1872 1873 1874 <p>Relative fields of time are used to indicate a period 1875 relative to today, like "Yesterday" or "Tomorrow". Some languages 1876 don't have words or short phrases for some of these. For example, 1877 English does not have a word for "the day before yesterday" as 1878 some languages do, such as "Vorgestern" in German.</p> 1879 1880 1881 1882 1883 <p> 1884 If your language doesn't have a natural term for one of these, 1885 please <b><i>do </i> <em>not</em></b> supply a translation: 1886 instead, pick the "inherited" value, such as <span 1887 class="fallback" title="Fallback from root"> <input 1888 title="#63133" disabled="disabled" value="V1" checked="checked" 1889 name="R1" type="radio">The day after tomorrow 1890 </span><span title="Fallback from root">. </span>The English phrase 1891 supplied here is just a placeholder to let you know what the field 1892 means, and is not part of the actual English locale data. 1893 </p> 1894 1895 1896 </td> 1897 1898 1899 </tr> 1900 1901 1902 <tr> 1903 1904 1905 <td>//ldml/dates/calendars/calendar.*/(a|p)m</td> 1906 1907 1908 <td> 1909 1910 1911 <h3>AM and PM</h3> 1912 1913 1914 1915 1916 <p> 1917 Note that even if your language doesn't use <b>am/pm</b> in any 1918 patterns, strings for those need to be defined for testing. As 1919 long as the 24 hour symbol (H) is used in the patterns, it won't 1920 show up in formatted times and dates. 1921 </p> 1922 1923 1924 </td> 1925 1926 1927 </tr> 1928 1929 1930 <tr> 1931 1932 1933 <td>//ldml/dates/calendars/calendar.*dateTimeFormatLength.*</td> 1934 1935 1936 <td> 1937 1938 1939 <h3>Date-Time Pattern</h3> 1940 1941 1942 1943 1944 <p>The date-time pattern is used to make a date + time out of 1945 separate date and time patterns. The date will be substituted for 1946 {1} and the time for {0}. It usually doesn't need to be changed.</p> 1947 1948 1949 </td> 1950 1951 1952 </tr> 1953 1954 1955 <tr> 1956 1957 1958 <td>.*narrow.*</td> 1959 1960 1961 <td> 1962 1963 1964 <h3>Narrow Date Fields</h3> 1965 1966 1967 1968 1969 <p>The narrow date fields are the shortest possible names (in 1970 terms of width in common fonts), and are not guaranteed to be 1971 unique. Think of what you might find on a credit-card-sized wallet 1972 or checkbook calendar, such as in English for days of the week:</p> 1973 1974 1975 1976 1977 <p> 1978 <i>S M T W T F S</i> 1979 </p> 1980 1981 1982 </td> 1983 1984 1985 </tr> 1986 1987 1988 <tr> 1989 1990 1991 <td>.*/eras.*</td> 1992 1993 1994 <td> 1995 1996 1997 <h3>Eras</h3> 1998 1999 2000 2001 2002 <p>There are only two values for an era in a Gregorian 2003 calendar, "BC" and "AD". These values can be translated into other 2004 languages, like "a.C." and and "d.C." for Spanish, but there are 2005 no other eras in the Gregorian calendar.</p> 2006 2007 2008 2009 2010 <p>Other calendars have a different numbers of eras. The names 2011 for eras are often specific to the given calendar, such as the 2012 Japanese era names. You only typically need to translate these if 2013 the calendar in question is in common use in one of the countries 2014 that uses your language.</p> 2015 2016 2017 </td> 2018 2019 2020 </tr> 2021 2022 2023 <tr> 2024 2025 2026 <td>.*/references.*</td> 2027 2028 2029 <td> 2030 2031 2032 <h3>References</h3> 2033 2034 2035 2036 2037 <p>References are used to document more controversial cases. 2038 Whenever there is a disagreement between translators, or when the 2039 choice of translation might not be understood, you should add a 2040 reference.</p> 2041 2042 2043 2044 2045 <ul> 2046 2047 2048 <li>Fill in a descriptive title for the reference, such as <strong>"The 2049 Economist Style Guide"</strong> 2050 2051 2052 <ul> 2053 2054 2055 <li>For examples of sources, see <a target="_blank" 2056 href="http://www.unicode.org/cldr/filing_bug_reports.html#Possible_Comparison_Sources">Possible 2057 Comparison Sources</a>. 2058 </li> 2059 2060 2061 <li>If available, add a web link in the 'URI' field, such 2062 as "<a target="_blank" 2063 href="http://publications.eu.int/code/es/es-5000500.htm">http://publications.eu.int/code/es/es-5000500.htm</a>". 2064 </li> 2065 2066 2067 <li>You can also use the format <strong>isbn:0-316-08215-5</strong> 2068 to refer to a book ISBN number in the URI field. 2069 </li> 2070 2071 2072 2073 2074 </ul> 2075 2076 2077 </li> 2078 2079 2080 <li>Click the <strong>Save</strong> button. You will see your 2081 new reference listed, and you can add it to other fields. 2082 </li> 2083 2084 2085 2086 2087 </ul> 2088 2089 2090 </td> 2091 2092 2093 </tr> 2094 2095 2096 <tr> 2097 2098 2099 <td>.*/exemplarCity.*</td> 2100 2101 2102 <td> 2103 2104 2105 <h3>Time Zone Exemplar Cities</h3> 2106 2107 2108 2109 2110 <p> 2111 For generic references to time zones, the country is used if 2112 possible, composed with a pattern that in English appears as "{0}<span 2113 style="background-color: rgb(192, 192, 192);"> Time</span>". Thus 2114 a time zone may appear as "Malaysia<span 2115 style="background-color: rgb(192, 192, 192);"> Time</span>" or "<span 2116 style="background-color: rgb(192, 192, 192);">Hora de </span>Malasia". 2117 If the country has multiple time zones, then a city is used to 2118 distinguish which one, thus "Argentina (La Rioja)<span 2119 style="background-color: rgb(192, 192, 192);"> Time</span>". 2120 </p> 2121 2122 2123 2124 2125 <p>Thus normally cities thus only need to be translated if they 2126 are in a country with multiple time zones.</p> 2127 2128 2129 </td> 2130 2131 2132 </tr> 2133 2134 2135 <tr> 2136 2137 2138 <td>.*(M|m)etazone.*</td> 2139 2140 2141 <td> 2142 2143 2144 <h3>Metazones</h3> 2145 2146 2147 2148 2149 <p> 2150 For some time zones, the survey tool will state that a particular 2151 <i>metazone</i> is in effect. A metazone is simply a grouping of 2152 time zones that share a common display name in customary usage. 2153 For example, 2154 <code>Europe/Paris</code> 2155 , 2156 <code>Europe/Berlin</code> 2157 , and many other time zones share a common display name "Central 2158 European Time", and have a common metazone 2159 <code>Europe_Central</code> 2160 . Use of a metazone allows us to translate this text only once 2161 while it can be use in many different time zones. The survey tool 2162 will show the default mappings for when a particular metazone was 2163 in use for a particular time zone. If you believe the mappings to 2164 be incorrect for your locality, please use the link to record any 2165 desired changes to the metazone mappings. Metazones have the same 2166 display fields as regular time zones, except that they have no 2167 exemplar city associated with them. 2168 </p> 2169 2170 2171 2172 2173 <p>Often there are situations where a particular time zone has 2174 an abbreviation, but the abbreviation is so seldom used that most 2175 people would not recognize it. The "commonlyUsed" field for a 2176 metazone is used to indicate that abbreviations for a particular 2177 time zone or metazone are in common use in the locale. You have 2178 two choices:</p> 2179 2180 2181 2182 2183 <ul> 2184 2185 2186 <li>If the GMT format would be understood better, set 2187 commonlyUsed to "false"</li> 2188 2189 2190 <li>Otherwise, if the abbriviation is commonly understood, 2191 set commonlyUsed to "true".</li> 2192 2193 2194 2195 2196 </ul> 2197 2198 2199 2200 2201 <p> 2202 For example: In English, PST is a commonly used abbreviation for 2203 "Pacific Standard Time", for the metazone 2204 <code> </code> 2205 <code>America_Pacific</code> 2206 . While NPT is an abbreviation for "Nepal Time", most English 2207 speakers would not recognize the meaning of "2:00 PM NPT". Thus, 2208 commonlyUsed should be <i>true</i> for 2209 <code>America_Pacific</code> 2210 (displaying, for example, 2:00 PM PST) and <i>false</i> for 2211 <code>Asia/Katmandu</code> 2212 (displaying, for example, "4:00 GMT+05:45"). 2213 </p> 2214 2215 2216 </td> 2217 2218 2219 </tr> 2220 2221 2222 <tr> 2223 2224 2225 <td>//ldml/posix/messages.*</td> 2226 2227 2228 <td> 2229 2230 2231 <h3>POSIX Yes and No</h3> 2232 2233 2234 2235 2236 <p>The POSIX yes and no strings should be whatever should count 2237 for "No" and "Yes" in your language, plus abbreviations. Don't 2238 worry about uppercases, that will be done automatically. Multiple 2239 forms can be entered separated by ":", such as "ne:n".</p> 2240 2241 2242 </td> 2243 2244 2245 </tr> 2246 2247 2248 <tr> 2249 2250 2251 <td>//ldml/layout/in(List|Text).*</td> 2252 2253 2254 <td> 2255 2256 2257 <h3>Casing Verification</h3> 2258 2259 2260 2261 2262 <p>These values can be used to help testing. If the value is 2263 set to anything but "mixed", then the items of that type will be 2264 checked whether they match, to help to catch inconsistencies. For 2265 example, if your language usually has the names of territories in 2266 lowercase, then set the value for territories to be 2267 "lowercase-words". The values are:</p> 2268 2269 2270 2271 2272 <table style="border-collapse: collapse;" id="table10" border="1" 2273 bordercolor="#009900" cellspacing="0"> 2274 2275 2276 <tbody> 2277 2278 <tr> 2279 2280 2281 <th style="vertical-align: top;"><strong>Values</strong></th> 2282 2283 2284 <td align="center"><strong>Example</strong></td> 2285 2286 2287 </tr> 2288 2289 2290 <tr> 2291 2292 2293 <td><code> 2294 <b>mixed</b> 2295 </code></td> 2296 2297 2298 <td>This is a mixture of Titlecase and lowercase.</td> 2299 2300 2301 </tr> 2302 2303 2304 <tr> 2305 2306 2307 <td><code> 2308 <b>lowercase-words</b> 2309 </code></td> 2310 2311 2312 <td>this is a mixture of titlecase and lowercase.</td> 2313 2314 2315 </tr> 2316 2317 2318 <tr> 2319 2320 2321 <td><code> 2322 <b>titlecase-words</b> 2323 </code></td> 2324 2325 2326 <td>This Is A Mixture Of Titlecase And Lowercase</td> 2327 2328 2329 </tr> 2330 2331 2332 <tr> 2333 2334 2335 <td><code> 2336 <b>titlecase-firstword</b> 2337 </code></td> 2338 2339 2340 <td>This is a mixture of titlecase and lowercase.</td> 2341 2342 2343 </tr> 2344 2345 2346 2347 2348 </tbody> 2349 2350 </table> 2351 2352 2353 2354 2355 <p> 2356 The <span class="forumlink"> <tt 2357 title="1-misc|casing|in_lists">layout/inList</tt></span> item has the 2358 same values, but a different use. It signals that if the items are 2359 put into a list (such as a menu on a computer), then they should 2360 be mechanically changed. For example, suppose that names of 2361 languages are normally lowercase, but when put into a menu they 2362 should normally have the first letter of the first word 2363 capitalized. If that's true, then you should set this value to 2364 <code> 2365 <b>titlecase-firstword</b> 2366 </code> 2367 . 2368 </p> 2369 2370 2371 2372 2373 <p>If that value is wrong for any individual item, then you can 2374 override that particular item by adding an "alt" value. To do so, 2375 contact your administrator.</p> 2376 2377 2378 </td> 2379 2380 2381 </tr> 2382 2383 2384 <tr> 2385 2386 2387 <td>//ldml/delimiters/.*</td> 2388 2389 2390 <td> 2391 2392 2393 <h3>Delimiters</h3> 2394 2395 2396 2397 2398 <p>Change this field if your language uses different quotation 2399 marks. The alternate forms are for embedded quotations, such as 2400 "He said 'Stop!'".</p> 2401 2402 2403 </td> 2404 2405 2406 </tr> 2407 2408 2409 <tr> 2410 2411 2412 <td>//ldml/dates/dateRangePattern.*</td> 2413 2414 2415 <td> 2416 2417 2418 <h3>Ranges of Dates</h3> 2419 2420 2421 2422 2423 <p>Modify this field to control how a range of dates appears, 2424 eg "Oct 12 - Nov 9".</p> 2425 2426 2427 </td> 2428 2429 2430 </tr> 2431 2432 2433 <tr> 2434 2435 2436 <td>//ldml/dates/timeZoneNames/fallbackFormat</td> 2437 2438 2439 <td> 2440 2441 2442 <h3>Country-Based Time Zone City Pattern</h3> 2443 2444 2445 2446 2447 <p>Modify this field to control the formatting of Country-Based 2448 time zone display when a country has multiple time zones, and the 2449 city is used to disambiguate them. In the pattern, {0} will be 2450 replaced by the city and {1} will be the country. This is normally 2451 not changed, except perhaps in languages that don't use spaces.</p> 2452 2453 2454 </td> 2455 2456 2457 </tr> 2458 2459 2460 <tr> 2461 2462 2463 <td>//ldml/dates/timeZoneNames/gmtFormat</td> 2464 2465 2466 <td> 2467 2468 2469 <h3>GMT Pattern</h3> 2470 2471 2472 2473 2474 <p> 2475 Modify this field if the format for GMT time uses different 2476 letters, such as <em>HUA+0200</em> for <em>GMT+02:00</em>, or if 2477 the letters GMT occur after the time. Make sure you include the <em>{0}</em>; 2478 that is where the actual time value will go! 2479 </p> 2480 2481 2482 </td> 2483 2484 2485 </tr> 2486 2487 2488 <tr> 2489 2490 2491 <td>//ldml/dates/timeZoneNames/hourFormat</td> 2492 2493 2494 <td> 2495 2496 2497 <h3>GMT Hours Pattern</h3> 2498 2499 2500 2501 2502 <p> 2503 This field controls the format for the time used with the GMT 2504 Pattern. It contains two patterns separated by a ";". The first 2505 controls positive time values (and zero), and the second controls 2506 the negative values. So to get <em>GMT+02.00</em> for positive 2507 values, and <em>GMT-02.00</em> for negative values, you'd use <em>+HH.mm;-HH.mm</em>. 2508 </p> 2509 2510 2511 </td> 2512 2513 2514 </tr> 2515 2516 2517 <tr> 2518 2519 2520 <td>//ldml/dates/timeZoneNames/regionFormat</td> 2521 2522 2523 <td> 2524 2525 2526 <h3>Country-Based Time Zone Pattern</h3> 2527 2528 2529 2530 2531 <p> 2532 For generic references to time zones, the country is used if 2533 possible, composed with a pattern that in English appears as "{0}<span 2534 style="background-color: rgb(192, 192, 192);"> Time</span>". Thus 2535 a time zone may appear as "Malaysia<span 2536 style="background-color: rgb(192, 192, 192);"> Time</span>" or "<span 2537 style="background-color: rgb(192, 192, 192);">Hora de </span>Malasia". 2538 If the country has multiple time zones, then a city is used to 2539 distinguish which one, thus "Argentina (La Rioja)<span 2540 style="background-color: rgb(192, 192, 192);"> Time</span>". 2541 </p> 2542 2543 2544 2545 2546 <p> 2547 Some languages would normally have grammatical adjustments 2548 depending on what the name of the city is. For example, one might 2549 need "12:43 pm <span style="background-color: rgb(192, 192, 192);">Tempo 2550 d'</span>Australia" but "12:43 pm <span 2551 style="background-color: rgb(192, 192, 192);">Tempo de</span><u> 2552 </u>Paris". In that case, there are two approaches: 2553 </p> 2554 2555 2556 2557 2558 <ol type="a"> 2559 2560 2561 <li>Use "{0}", which will give results like "12:43 pm 2562 Australia" and "12:43 pm Paris", or</li> 2563 2564 2565 <li>Use a "form-style" phrasing such as "<span 2566 style="background-color: rgb(192, 192, 192);">Tempo de: </span>{0}", 2567 which will give results like "12:43 pm <span 2568 style="background-color: rgb(192, 192, 192);">Tempo de: </span>Australia" 2569 and "12:43 pm <span style="background-color: rgb(192, 192, 192);">Tempo 2570 de: </span>Paris". 2571 </li> 2572 2573 2574 2575 2576 </ol> 2577 2578 2579 </td> 2580 2581 2582 </tr> 2583 2584 2585 <tr> 2586 2587 2588 <td>//ldml/dates/.*/days/.*</td> 2589 2590 2591 <td> 2592 2593 2594 <h3>Days of the Week</h3> 2595 2596 2597 2598 2599 <p>This field is one of the days of the week, such as Sunday or 2600 Monday.</p> 2601 2602 2603 </td> 2604 2605 2606 </tr> 2607 2608 2609 <tr> 2610 2611 2612 <td>.*/timeZoneNames.*</td> 2613 2614 2615 <td> 2616 2617 2618 <h3 align="left">Time Zones</h3> 2619 2620 2621 2622 2623 <p align="left"> 2624 In the standard used for time zones, a <i>time zone</i> is an area 2625 of a country that has consistent behavior in terms of its offset 2626 from Greenwich Mean Time. In particular, within that zone, the 2627 same daylight-savings (summer-time) behavior is observed, now and 2628 in the past and future (as far as is known). This means that time 2629 zones are fairly fine granularity, as you can see by consulting <span 2630 class="loser"> <a target="_blank" 2631 href="http://www.unicode.org/cldr/data/charts/supplemental/territory_containment_un_m_49.html">Territory 2632 Containment</a>. 2633 </span>The name of the time zone is taken from the most populous city, 2634 such as <b><code>America/Denver</code></b>. Here are some examples 2635 of time zones, and why they are distinct from <b><code>America/Denver</code></b>. 2636 </p> 2637 2638 2639 2640 2641 <table style="border-collapse: collapse;" id="table11" border="1" 2642 bordercolor="#009900" cellspacing="0"> 2643 2644 2645 <tbody> 2646 2647 <tr> 2648 2649 2650 <th style="vertical-align: top;"><strong>Time zone</strong></th> 2651 2652 2653 <td align="center"><strong>Reason</strong></td> 2654 2655 2656 </tr> 2657 2658 2659 <tr> 2660 2661 2662 <td><b><code>America/Chicago</code></b></td> 2663 2664 2665 <td>Chicago has a different standard offset from GMT (6 2666 hours) than Denver (7 hours).</td> 2667 2668 2669 </tr> 2670 2671 2672 <tr> 2673 2674 2675 <td><b><code>America/Phoenix</code></b></td> 2676 2677 2678 <td>While Phoenix has the same GMT offset as Denver, it 2679 doesn't have daylight savings time, while Denver does.</td> 2680 2681 2682 </tr> 2683 2684 2685 <tr> 2686 2687 2688 <td><b><code>America/Edmonton</code></b></td> 2689 2690 2691 <td>Although Edmonton has the same offset and daylight 2692 savings behavior as Denver, it is in a different country</td> 2693 2694 2695 </tr> 2696 2697 2698 2699 2700 </tbody> 2701 2702 </table> 2703 2704 2705 2706 2707 <p align="left"> 2708 <span class="loser">Time zones can be displayed in a 2709 variety of ways, depending on the environment and program 2710 requirements. Here are some examples:</span> 2711 </p> 2712 2713 2714 2715 2716 <table style="border-collapse: collapse;" id="table12" border="1" 2717 bordercolor="#009900" cellspacing="0"> 2718 2719 2720 <caption> 2721 <b>Sample Time Zone Formats</b> 2722 </caption> 2723 <tbody> 2724 2725 <tr> 2726 2727 2728 <th style="vertical-align: top;">Named</th> 2729 2730 2731 <th style="vertical-align: top;"><strong>List 2732 Format</strong></th> 2733 2734 2735 <td align="center"><b>Abbreviated</b></td> 2736 2737 2738 <td colspan="2" align="center"><strong>With a Time</strong></td> 2739 2740 2741 </tr> 2742 2743 2744 <tr> 2745 2746 2747 <td rowspan="2">Country-Based</td> 2748 2749 2750 <td colspan="2" align="center">United States (Los Angeles) 2751 Time</td> 2752 2753 2754 <td colspan="2">12:43 pm United States (Los Angeles) Time</td> 2755 2756 2757 </tr> 2758 2759 2760 <tr> 2761 2762 2763 <td colspan="2" align="center">Italy Time</td> 2764 2765 2766 <td colspan="2">12:43 pm Italy Time</td> 2767 2768 2769 </tr> 2770 2771 2772 <tr> 2773 2774 2775 <td rowspan="3">Named 2776 2777 <p> </p> 2778 2779 2780 </td> 2781 2782 2783 <td align="center">Pacific Time</td> 2784 2785 2786 <td align="center">PT</td> 2787 2788 2789 <td>12:43 pm Pacific Time</td> 2790 2791 2792 <td>12:43 pm PT</td> 2793 2794 2795 </tr> 2796 2797 2798 <tr> 2799 2800 2801 <td align="center">Central European Time</td> 2802 2803 2804 <td align="center">CET</td> 2805 2806 2807 <td>12:43 pm Central European Time</td> 2808 2809 2810 <td>12:43 pm CET</td> 2811 2812 2813 </tr> 2814 2815 2816 <tr> 2817 2818 2819 <td align="center">Pacific Standard Time</td> 2820 2821 2822 <td align="center">PST</td> 2823 2824 2825 <td>12:43 pm Pacific Standard Time</td> 2826 2827 2828 <td>12:43 pm PST</td> 2829 2830 2831 </tr> 2832 2833 2834 <tr> 2835 2836 2837 <td rowspan="2">GMT</td> 2838 2839 2840 <td colspan="2" align="center">GMT-8:00</td> 2841 2842 2843 <td colspan="2">12:43 pm GMT-8:00</td> 2844 2845 2846 </tr> 2847 2848 2849 <tr> 2850 2851 2852 <td colspan="2" align="center">GMT+2:00</td> 2853 2854 2855 <td colspan="2">12:43 pm GMT+2:00</td> 2856 2857 2858 </tr> 2859 2860 2861 2862 2863 </tbody> 2864 2865 </table> 2866 2867 2868 2869 2870 <p align="left">These are composed from different pieces that 2871 you translate.</p> 2872 2873 2874 2875 2876 <ul> 2877 2878 2879 <li> 2880 2881 2882 <p align="left">For the country-based formats, you'll be 2883 translating the country names anyway, but also city names where 2884 a country has multiple zones. You'll also be translating a 2885 pattern for the "Time" portion (or leaving it blank if that is 2886 better for your language).</p> 2887 2888 2889 </li> 2890 2891 2892 <li> 2893 2894 2895 <p align="left"> 2896 For the named formats, you'll have the opportunity to translate 2897 specific names for that zone, or names common to groupings of 2898 time zones (called <i>metazones</i>) that span multiple time 2899 zones. You have 6 possible strings to translate: generic 2900 (Pacific Time), standard (Pacific Standard Time), daylight 2901 (Pacific Daylight Time), plus abbreviations of those.<i><b> 2902 You only want to provide names (and especially abbreviations) 2903 where those are customarily understood by speakers of your 2904 language. Just because they are in English doesn't mean they 2905 should always be translated in your language.</b></i> 2906 </p> 2907 2908 2909 </li> 2910 2911 2912 <li> 2913 2914 2915 <p align="left">For the GMT format, you'll be translating the 2916 term "GMT" (if necessary for your language), and the format for 2917 the hours (eg, +8:45 vs. +8.45).</p> 2918 2919 2920 </li> 2921 2922 2923 2924 2925 </ul> 2926 2927 2928 </td> 2929 2930 2931 </tr> 2932 2933 2934 <tr> 2935 2936 2937 <td>//ldml/dates/.*/months/.*</td> 2938 2939 2940 <td> 2941 2942 2943 <h3>Months of the Year</h3> 2944 2945 2946 2947 2948 <p>This field is one of the months of the year, such as January 2949 or February.</p> 2950 2951 2952 </td> 2953 2954 2955 </tr> 2956 2957 2958 <tr> 2959 2960 2961 <td>//ldml/fallback</td> 2962 2963 2964 <td> 2965 2966 2967 <h3>Locale Fallbacks</h3> 2968 2969 2970 2971 2972 <p> 2973 You should add here a list of locales that would be most natural 2974 to use when no translation is available (this is called a <i>fallback)</i>. 2975 This is especially useful for minority languages. For example, for 2976 Breton [br] the most natural language to fall back to might be 2977 French [fr], that is, to use French names for countries that 2978 aren't translated. Similarly, the fallback for Moldavian [mo] 2979 might be Romanian [ro]. 2980 </p> 2981 2982 2983 <p style="font-style: italic;"> 2984 Fallbacks should <span style="font-weight: bold;">only</span> be 2985 included if a substantial majority of people speaking the language 2986 in question would be likely to understand the fallback language. 2987 If there are no such languages, the fallback field should be left 2988 blank. 2989 </p> 2990 2991 2992 <p> 2993 Fallbacks can take the script or region into account; the fallback 2994 for Northern Sámi (Finland) [se-FI] might be Finnish (Finland) 2995 [fi-FI], while the fallback for Northern Sámi [se] generally might 2996 be Norwegian [nb].<br> 2997 2998 </p> 2999 3000 3001 <p> 3002 The values you need to use are locale codes, <span 3003 style="font-style: italic;">not the names or translations;</span> 3004 thus you would put in 3005 <code>fr</code> 3006 or 3007 <code>fr_BE</code> 3008 ,<i> not</i> "French" or "<span class="loser">français</span>". If 3009 you don't know the codes for the languages in question, you can 3010 consult the survey tool <a 3011 href="http://unicode.org/cldr/apps/survey?p_codes=t" 3012 target="_blank">Locales</a>, or the <a 3013 href="http://www.iana.org/assignments/language-subtag-registry" 3014 target="_blank">BCP 47 registry</a>. 3015 </p> 3016 3017 3018 <p>Multiple fallback languages can be entered in order of 3019 priority, separated by spaces, for example: nl en.</p> 3020 3021 3022 </td> 3023 3024 3025 </tr> 3026 3027 <tr> 3028 3029 <td>//ldml/(units/unit|numbers/currencies/currency.*/displayName).*</td> 3030 3031 <td> 3032 3033 <h3>Localized Units</h3> 3034 3035 3036 <p> 3037 Localized units provide more natural ways of expressing unit 3038 phrases that vary in plural form, such as "1 hour" vs "2 hours". 3039 While they cannot express all the intricacies of natural 3040 languages, they allow for more natural phrasing than constructions 3041 like "1 hour(s)".<span style="font-style: italic; color: black;"></span><span 3042 style="font-family: monospace;"></span><span 3043 style="font-style: italic;"><span 3044 style="color: rgb(153, 0, 0); font-weight: bold;"></span></span> 3045 </p> 3046 3047 3048 <p style="font-style: italic;"> 3049 <span style="color: rgb(153, 0, 0); font-weight: bold;">Please </span>review 3050 the draft rules that CLDR is using for plurals for your language, 3051 at <a target="_blank" 3052 href="http://www.unicode.org/cldr/data/charts/supplemental/language_plural_rules.html">Language 3053 Plural Rules</a>, and the description there about the plural 3054 categories. 3055 </p> 3056 3057 3058 <p> 3059 Each unit may have multiple plural forms, one for each category. 3060 These are composed with numbers using a <span 3061 style="font-style: italic;">unitPattern</span> of the form "{0} 3062 {1}". A formatted number will be substituted in place of the 3063 "{0}", while the unit value will be subsituted in place of the 3064 "{1}". 3065 </p> 3066 3067 3068 <p> 3069 For example, for English if the unit is an <span 3070 style="font-family: monospace;">hour</span> and the number is <span 3071 style="font-family: monospace;">1234</span>, then the number is 3072 looked up to get the rule category <span 3073 style="font-family: monospace;">other</span>. The number is then 3074 formatted into "1,234" and composed with the unitName for <span 3075 style="font-family: monospace;">other</span> and the unitPattern 3076 for <span style="font-family: monospace;">other</span> to get the 3077 final result. Examples are in the table below. 3078 </p> 3079 3080 3081 <table style="border-collapse: collapse;" id="table11" border="1" 3082 bordercolor="#009900" cellspacing="0"> 3083 3084 3085 <tbody> 3086 3087 <tr> 3088 3089 3090 <th>Locale</th> 3091 3092 <th style="vertical-align: top;"><strong>Unit</strong></th> 3093 3094 3095 <th style="text-align: center;"><strong>Number</strong></th> 3096 3097 <th>Formatted number</th> 3098 3099 <th>Plural category</th> 3100 3101 <th>unitName for category</th> 3102 3103 <th>unitPattern for category</th> 3104 3105 <th>Final Result</th> 3106 3107 3108 </tr> 3109 3110 3111 <tr> 3112 3113 <td style="font-family: monospace;">en</td> 3114 3115 <td style="text-align: center;"><b><code>hour</code></b></td> 3116 3117 <td style="text-align: center; font-family: monospace;">0</td> 3118 3119 <td style="text-align: center;">"0"</td> 3120 3121 <td style="text-align: center; font-family: monospace;">other</td> 3122 3123 <td style="text-align: center;">"hours"</td> 3124 3125 <td style="text-align: center;">"{0} {1}"</td> 3126 3127 <td style="text-align: center;">"0 hours"</td> 3128 3129 </tr> 3130 3131 <tr> 3132 3133 <td style="font-family: monospace;">en</td> 3134 3135 <td style="text-align: center;"><b><code>hour</code></b></td> 3136 3137 <td style="text-align: center; font-family: monospace;">1</td> 3138 3139 <td style="text-align: center;">"1"</td> 3140 3141 <td style="text-align: center; font-family: monospace;">one</td> 3142 3143 <td style="text-align: center;">"hour"</td> 3144 3145 <td style="text-align: center;">"{0} {1}"</td> 3146 3147 <td style="text-align: center;">"1 hour"</td> 3148 3149 </tr> 3150 3151 <tr> 3152 3153 3154 <td style="font-family: monospace;">en</td> 3155 3156 <td style="text-align: center;"><b><code>hour</code></b></td> 3157 3158 3159 <td style="text-align: center; font-family: monospace;">1234</td> 3160 3161 <td style="text-align: center;">"1,234"</td> 3162 3163 <td style="text-align: center; font-family: monospace;">other</td> 3164 3165 <td style="text-align: center;">"hours"</td> 3166 3167 <td style="text-align: center;">"{0} {1}"</td> 3168 3169 <td style="text-align: center;">"1,234 hours"</td> 3170 3171 3172 </tr> 3173 3174 <tr> 3175 3176 <td style="font-family: monospace;">fr</td> 3177 3178 <td style="text-align: center;"><b><code>hour</code></b></td> 3179 3180 <td style="text-align: center; font-family: monospace;">0</td> 3181 3182 <td style="text-align: center;">"0"</td> 3183 3184 <td 3185 style="text-align: center; font-family: monospace; background-color: rgb(255, 204, 204);">one</td> 3186 3187 <td style="text-align: center;">"heure"</td> 3188 3189 <td style="text-align: center;">"{0} {1}"</td> 3190 3191 <td style="text-align: center;">"0 heure"</td> 3192 3193 </tr> 3194 3195 <tr> 3196 3197 <td style="font-family: monospace;">fr</td> 3198 3199 <td style="text-align: center;"><b><code>hour</code></b></td> 3200 3201 <td style="text-align: center; font-family: monospace;">1</td> 3202 3203 <td style="text-align: center;">"1"</td> 3204 3205 <td style="text-align: center; font-family: monospace;">one</td> 3206 3207 <td style="text-align: center;">"heure"</td> 3208 3209 <td style="text-align: center;">"{0} {1}"</td> 3210 3211 <td style="text-align: center;">"1 heure"</td> 3212 3213 </tr> 3214 3215 <tr> 3216 3217 <td style="font-family: monospace;">fr</td> 3218 3219 <td style="text-align: center;"><b><code>hour</code></b></td> 3220 3221 <td style="text-align: center; font-family: monospace;">1234</td> 3222 3223 <td style="text-align: center;">"1 234"</td> 3224 3225 <td style="text-align: center; font-family: monospace;">other</td> 3226 3227 <td style="text-align: center;">"heures"</td> 3228 3229 <td style="text-align: center;">"{0} {1}"</td> 3230 3231 <td style="text-align: center;">"1 234 heures"</td> 3232 3233 </tr> 3234 3235 3236 3237 3238 3239 3240 </tbody> 3241 3242 </table> <span class="loser"></span> 3243 3244 <p> 3245 There is one "default" <span style="font-style: italic;">unitPattern</span> 3246 for each plural category, listed under the unit "one". If the 3247 particular unit needs a special <span 3248 style="font-style: italic;">unitPattern</span> for a particular 3249 plural category, then one can also be added. That is, suppose that 3250 for a particular language, in the plural the number goes after the 3251 translation of <span style="font-style: italic;">hour</span> 3252 instead of before. Then for the unit <span 3253 style="font-family: monospace;">hour</span>, and plural category 3254 <span style="font-family: monospace;">other</span>,<span 3255 style="font-family: monospace;"> </span>the <span 3256 style="font-style: italic;">unitPattern</span> can be different 3257 if needed. 3258 </p> 3259 3260 3261 <p>The key is, if the examples look ok you shouldn't need to do 3262 anything.</p> 3263 3264 3265 <p> 3266 To request a change in the plural rules, please file a request in 3267 a <a target="_blank" 3268 href="http://unicode.org/cldr/bugs/locale-bugs">bug report</a>. 3269 </p> 3270 3271 </td> 3272 3273 </tr> 3274 3275 <tr> 3276 3277 <td>//ldml/localeDisplayNames/localeDisplayPattern/localePattern.*</td> 3278 3279 <td> 3280 3281 <h3>Locale Display Patterns</h3> <br> Locale display patterns 3282 are used to format a compound language (locale) name such as 3283 'en_AU' or 'uz_Arab'. The pattern is something like "{0} ({1})". 3284 When the locale is formatted, the language is substituted for {0}, 3285 and the region or script for {1}. <br> 3286 3287 3288 <p>For example, take "en_AU". First the language code 'en' is 3289 translated, such as to "anglais", then the country is translated, 3290 such as "Australie". The patterns is used to put those together, 3291 into something like "anglais (Australie)". This works the 3292 same way if there is a script; for example, "uz-Arab" => 3293 "ouzbek (arabe)".</p> If there is both a script and a region, then a 3294 list is formed using the <span style="font-style: italic;">separator</span>, 3295 then {1} is replaced by that list, such as "uz-Arab-AF" => 3296 "ouzbek (arabe, Afghanistan)"<br> 3297 3298 3299 <p>For certain compound language (locale) names, you can also 3300 supply specific translations. Thus for the whole locale 'en_GB', 3301 you can provide a translation like "Australian English".</p> 3302 3303 </td> 3304 3305 </tr> 3306 3307 <tr> 3308 3309 <td>//ldml/localeDisplayNames/codePatterns/codePattern.*</td> 3310 3311 <td> 3312 3313 <h3>Code Patterns</h3> Code patterns are used in lists where the 3314 name of the language, script, or region is not available -- the 3315 code (like "de" for German) will be substituted for the {0} 3316 placeholder. Thus you if the language code 'zaz' is not 3317 translated in your language, you might see in a list something 3318 like:<br> 3319 3320 3321 <ul> 3322 3323 <li>English</li> 3324 3325 <li>French</li> 3326 3327 <li>Language: zaz</li> 3328 3329 <li>Spanish</li> 3330 3331 3332 </ul> The last line is the result of substituting the code 'zaz' into 3333 the code pattern. You can choose the pattern that makes sense for 3334 your language; if the best choice is to just use the code alone, 3335 then use {0}. 3336 </td> 3337 3338 </tr> 3339 3340 3341 3342 </tbody> 3343 </table> 3344 3345 3346 <p> 3347 The text to insert can be fairly arbitrary HTML. The software that 3348 reads this table will search the first column (eg between <td> 3349 and </td>) and return the contents of the second column. We plan 3350 on adding a few variables also, for the current locale name, in 3351 particular. This file uses the survey tool style-sheet, so you can use 3352 those <span class="winner">styles</span> (and icons, like <a 3353 target="target=" surveytool:n:de="" class="forumlink" 3354 href="http://unicode.org/cldr/apps/survey?_=de&forum=de&xpath=249"> 3355 <img alt="[stop]" style="width: 16px; height: 16px;" 3356 src="http://unicode.org/cldr/apps/stop.png" 3357 title="Errors - please zoom in" border="0"> 3358 </a>) in the text to insert. 3359 </p> 3360 3361 3362 <p> 3363 <b>WARNING</b> 3364 </p> 3365 3366 3367 <ul> 3368 3369 3370 <li><b><i>It uses a very dumb parser, so make sure that 3371 table elements are matched, eg <td> with </td>, and 3372 also that <tr>, </tr>, <table>, and 3373 </table> are on separate lines.</i></b></li> 3374 3375 3376 <li><b><i>The regular expression for the path must match 3377 the whole path, so if it is an interior substring, remember to add 3378 .* on both ends.</i></b></li> 3379 3380 3381 <li><b><i>Run TestUtilities.testExampleGenerator() to 3382 verify that everything works.</i></b></li> 3383 3384 3385 </ul> 3386 3387 3388 3389</body> 3390</html> 3391
