You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a new “-relative” variant for [Date-Time Combined Formats](/translation/date-time/date-time-patterns#date-time-combined-formats).
65
+
#### New “relative” variant for date-time combining pattern
66
+
67
+
There is a new “-relative” variant for [Date-Time Combined Formats](/translation/date-time/date-time-patterns#date-time-combined-formats). [CLDR-18350](https://unicode-org.atlassian.net/browse/CLDR-18350)
51
68
52
69
Before CLDR 48, there were two variants:
53
70
- A “standard” variant for combining date with time, typically without literal text. In English this was “{1}, {0}”
@@ -61,9 +78,69 @@ of a relative date and a single time. If you do not supply this, that combinatio
61
78
in English that would produce “tomorrow, 3:00 PM”. If instead you want the same combining behavior for a relative date with a single time as for a
62
79
fvfixed date with single time (as was the case in CLDR 47 and earlier), then for each length style copy the existing “atTime” form to the new “relative” form.
63
80
64
-
### Metazones
81
+
### Timezones, metazones and exemplar cities
82
+
83
+
#### New `gmtUnknownFormat`
84
+
85
+
Normally time zones formatted using UTC offset (like xxxx) use the `gmtFormat` pattern (“GMT{0}” in root). The new `gmtUnknownFormat` is used when formatting time zones using a UTC offset for cases when the offset or zone is unknown. The root value “GMT+?” need not be changed if it works for your locale; hoever it should be consistent with the `gmtFormat` and `gmtZeroFormat` in your locale. See [Time Zones and City names](translation/time-zones-and-city-names)[CLDR-18236](https://unicode-org.atlassian.net/browse/CLDR-18236)
86
+
87
+
#### “Unknown City” → “Unknown Location”
88
+
89
+
For zone `Etc/Unknown`, the exemplarCity name was changed in English from “Unknown City” to “Unknown Location”; other locales should update accordingly. [CLDR-18262](https://unicode-org.atlassian.net/browse/CLDR-18262)
90
+
91
+
#### Changes to the root and/or English names of many exemplar cities and some metazones
There actually added in CLDR 42 per (CLDR-14336)[https://unicode-org.atlassian.net/browse/CLDR-14336]. However, they were not properly set up for coverage and inheritance, and were not presented to many vetters. These issue were corrected in CLDR 47 per [CLDR-17879](https://unicode-org.atlassian.net/browse/CLDR-17879), which adjusted the data for some locales (and made it draft="provisional"). Many vetters will see these for the first time in CLDR 48.
100
+
- The `alphaNextToNumber` patterns should be used when currency symbol is alphabetic, such as “USD”; in this case the m=pattern may add a space to offset the currency symbol from the numeric value, if the standard pattern does not already include a space.
101
+
- The `alphaNextToNumber` patterns should be used when the currency amount should be formatted without a currency symbol, as in a table of values all using the same currency. This pattern must not include the currency symbol pattern character ‘¤’.
102
+
103
+
For more information see [Number and currency patterns](/translation/number-currency-formats/number-and-currency-patterns).
104
+
105
+
#### Rational formats
106
+
107
+
These describe the formatting of rational fractions such as ¾ or combinations of integers and fractions such as 5½. [CLDR-17570](https://unicode-org.atlassian.net/browse/CLDR-17570)
108
+
109
+
Here are the the English values and a short description of their purpose; for more information see (TBD):
110
+
-`rationalFormats-rationalPattern`: “{0}⁄{1}” - The format for a rational fraction with arbitrary numerator and denominator; the English pattern uses the Unicode character ‘⁄’ U+2044 FRACTION SLASH which causes composition of fractions such as 22⁄7.
111
+
-`rationalFormats-integerAndRationalPattern`: “{0} {1}” - The format for combining an integer with a rational fraction composed using the pattern above; the English pattern uses U+202F NARROW NO-BREAK SPACE (NNBSP) to produce a small no-break space.
112
+
-`rationalFormats-integerAndRationalPattern-superSub`: “{0}{1}” - The format for combining an integer with a rational fraction using (TBD); the English pattern uses U+2060 WORD JOINER, a zero-width no-break space.
113
+
-`rationalFormats-rationalUsage`: “sometimes” - An indication of the extent to which rational fractions are used in the locale; may be one of “never”, “sometimes”, ... (TBD)
114
+
115
+
### Units
116
+
117
+
#### Rework certain concentration units
118
+
119
+
The keys for two units changed (the translations can probably remain the same) and there is one new unit that is used for constructing certain other kinds of concentration units. [CLDR-18274](https://unicode-org.atlassian.net/browse/CLDR-18274):
120
+
- key `permillion` changed to `concentr-part-per-1e6`; English values remain “parts per million”, “{0} part per million”, etc.
121
+
- key `portion-per-1e9` changed to `concentr-part-per-1e9`; English values remain “parts per billion”, “{0} part per billion”, etc.
122
+
- new key `part` used for constructing arbitrary concentrations such as “parts per 100,000”; English values “parts”, “{0} part”, etc.
123
+
124
+
#### Many new units in English
125
+
126
+
Mnny new units were added in English. In general these are very specific and vetters will not be
127
+
asked to translate them for other locales, so coverage will be comprehensive. If some of these units
128
+
would be useful in particualr locales, please file a ticekt and the coverage can be adjusted.
0 commit comments