Milestone Schedule

Corrigenda

This page lists corrigenda to versions of CLDR. Problems that do not rise to the level of a corrigendum are found on CLDR Errata.

Each release of CLDR is a stable release and may be used as reference material or cited as a normative reference by other specifications. Each version, once published, is absolutely stable and will never change. However, implementations may and are encouraged to apply these corrigenda to their use of an appropriate version. For example, an implementation may claim conformance to CLDR 1.3, as amended by Corrigendum 1.

Corrigendum 1: Time zone and Date Format Pattern Correction

In CLDR version 1.3, the policy was that for a given (resolved) locale, uniqueness is required for time zone display names. That is, two different time zone IDs could not have the same display name. This policy turns out to be overly strict, and did not allow for customary names in cases where it does not cause a problem. The committee has relaxed this policy so that where the parsing results would give the same GMT offset, the standard and daylight display names can be the same across different time zone IDs.

The short and long time zone names for Europe/London and Europe/Dublin in the en.xml locale data file had been changed because of the old policy. In accordance with this new policy, they are corrected by this corrigendum as follows:

CLDR 1.3 Corrected
<zone type="Europe/London">
  <long>
    <generic>British Time</generic>
    <standard>British Standard Time</standard>
    <daylight>British Daylight Time</daylight>
  </long>
  <short>
    <generic>BT</generic>
    <standard>BST</standard>
    <daylight>BDT</daylight>
  </short>
</zone>
<zone type="Europe/London">
  <long>
    <standard>Greenwich Mean Time</standard>
    <daylight>British Summer Time</daylight>
  </long>
  <short>
    <standard>GMT</standard>
    <daylight>BST</daylight>
  </short>
</zone>

{omitted}

<zone type="Europe/Dublin">
  <long>
    <standard>Greenwich Mean Time</standard>
    <daylight>Irish Summer Time</daylight>
  </long>
  <short>
    <standard>GMT</standard>
    <daylight>IST</daylight>
  </short>
</zone>

The data reflecting the above correction is checked into CVS under the tag release-1-3-C1. For information on the usage of this, see CLDR Releases (Downloads).

The following are corrections to the date format pattern in UTS #35: Locale Data Markup Language (LDML). The Stand-Alone months and days, and the long era names, although approved by the technical committee, had been omitted from the specification. The use of specific sequences of 'z', 'Z', and 'E' is changed to preserve backwards compatibility with Java.

CLDR 1.3 Corrected
era G 1..3 AD Era - Replaced with the Era string for the current date.
era G 1..3 AD Era - Replaced with the Era string for the current date. One to three letters for the abbreviated form, four letters for the long form.
4 Anno Domini
month M 1..2 09 Month - Use one or two for the numerical month, three for the abbreviation, or four for the full name, or 5 for the narrow name.
3 Sept
4 September
5 S
month M 1..2 09 Month - Use one or two for the numerical month, three for the abbreviation, or four for the full name, or five for the narrow name.
3 Sept
4 September
5 S
L 1..2 09 Stand-Alone Month - Use one or two for the numerical month, three for the abbreviation, or four for the full name, or 5 for the narrow name.
3 Sept
4 September
5 S
week
day
E 1..2 3 Day of week - Use three for the short day, or four for the full name, or 5 for the narrow name. Sunday is always day 1
3 Tues
4 Tuesday
5 T
e 1..2 2 Local day of week. Same as E except numeric value will depend on the local starting day of the week. For this example, Monday is the first day of the week.
3 Tues
4 Tuesday
5 T
week
day
E 1..3 Tues Day of week - Use one through three letters for the short day, or four for the full name, or five for the narrow name.
4 Tuesday
5 T
e 1..2 2 Local day of week. Same as E except adds a numeric value that will depend on the local starting day of the week, using one or two letters. For this example, Monday is the first day of the week.
3 Tues
4 Tuesday
5 T
c 1 2 Stand-Alone local day of week - Use one letter for the local numeric value (same as 'e'), three for the short day, or four for the full name, or five for the narrow name.
3 Tues
4 Tuesday
5 T
zone z 1 PT Time zone. Use 1 for short wall (generic) time, 2 for long wall time, 3 for the short time zone (i.e. PST) or 4 for the full name (Pacific Standard Time). If there's no name for the zone, fallbacks may be used, depending on available data.
2 Pacific Time
3 PDT
4 Pacific Daylight Time
Z 1 GMT-08:00 Use 1 for GMT format, 2 for RFC 822
2 -0800
zone z 1..3 PDT Time zone - Use one to three letters for the short time zone or four for the full name. For more information, see Appendix J: Time Zone Fallback
4 Pacific Daylight Time
Z 1..3 -0800 Use one to three letters for RFC 822, four letters for GMT format.
4 GMT-08:00
v 1 PT Use one letter for short wall (generic) time, four for long wall time. For more information, see Appendix J: Time Zone Fallback
4 Pacific Time
Comments