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
Copy file name to clipboardExpand all lines: docs/site/translation.md
+67-19Lines changed: 67 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,38 +33,60 @@ Most of the following are relevant to locales at the Modern Coverage Level.
33
33
34
34
### New emoji
35
35
36
-
TBD - New emoji will be added the week of April 21st.
36
+
New emoji will be added the week of April 21st.
37
+
38
+
### Core Data
39
+
There are new Alphabetic Information items.
40
+
-`numbers-auxiliary` — If there are are characters used in numbers that are not customarily used, but may occur, add them here instead of in `auxiliary`.
41
+
-`punctuation-auxiliary` — If there are punctuation characters that are not customarily used, but may occur, add them here instead of in `auxiliary`.
42
+
-`punctuation-person` — If there are punctuation characters that are customarily used in people's names in standard documents, add them here.
43
+
This should be a small list such as “.” or “-”.
44
+
Do **not** include ‘fanciful’ characters such as emoji or [kaomoji](https://en.wikipedia.org/wiki/Kaomoji).
37
45
38
46
### Locale display names
39
47
40
48
#### More language names
41
49
42
-
As new locales reach Basic Coverage, their language names have been added for locales targeting modern coverage: TBD
50
+
As new locales reach Basic Coverage, their language names have been added for locales targeting modern coverage. These include: **TBD**
43
51
44
52
#### Languages whose English name changed
45
53
46
-
- tkl: English name changed to Tokelauan. [CLDR-11231](https://unicode-org.atlassian.net/browse/CLDR-11231)
54
+
- tkl: English name changed to Tokelauan.
55
+
<!-- Let's not add ticket numbers, except for Known Issues — there is already enough for vetters to read, and the tickets will often be confusing to people or take more time to read and puzzle out than is worth it. Fine to leave them in the document, but commented out, for our usage.
There is a new mechanism for better menu names. When you see a **Code** with `-core` or `-extension`, please read [Core and Extensions](/displaynames/languagelocale-names#core-and-extensions).
47
61
48
62
#### Scripts
49
63
50
64
There are 5 new scripts for Unicode 17. Currently the names are in English: Beria Erfe, Chisoi, Sidetic, Tai Yo, Tolong Siki.
51
-
Coverage for other languages is at comprehensive; if there is a need to have coverage at lower level in some locale,
52
-
please file a ticket. [CLDR-18283](https://unicode-org.atlassian.net/browse/CLDR-18283)
65
+
Coverage for other languages is at comprehensive.
66
+
<!-- I don't think we want to encourage this: ... if there is a need to have coverage at lower level in some locale,
67
+
please file a ticket. [CLDR-18283](https://unicode-org.atlassian.net/browse/CLDR-18283) -->
53
68
54
-
#### ISO 8601 calendar name
69
+
#### ISO 8601 calendar
55
70
56
71
This is a variant of the Gregorian calendar whose formats always use year-month-day ordering and a 24-hour time cycle.
57
72
The English name has changed to reflect that (and also added a variant); locales should update accordingly:
58
-
-calendar-iso8601: Gregorian (Year First)
59
-
-calendar-iso8601-variant: ISO 8601 Order
73
+
- calendar-iso8601: Gregorian (Year First)
74
+
- calendar-iso8601-variant: ISO 8601 Order
75
+
76
+
Please go though the ISO8601 fields. You should change separators to match what is acceptable in your language. However, do not change the ordering of the elements, which should be strictly the following order (for any that occur in a particular pattern):
77
+
* year - month - day - day-of-week - hour - minute - second
Also avoid changing the width of numeric fields (like `dd`).
80
+
81
+
<!-- Let's not add ticket numbers — there is already enough for vetters to read, and the tickets will often be confusing to people or take more time to read and puzzle out than is worth it. Fine to leave them here, commented out, for our usage.
#### New “relative” variant for date-time combining pattern
66
87
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)
88
+
There is a new “-relative” variant for [Date-Time Combined Formats](/translation/date-time/date-time-patterns#date-time-combined-formats).
- A “standard” variant for combining date with time, typically without literal text. In English this was “{1}, {0}”
@@ -82,11 +104,13 @@ fvfixed date with single time (as was the case in CLDR 47 and earlier), then for
82
104
83
105
#### New `gmtUnknownFormat`
84
106
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)
107
+
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; however it should be consistent with the `gmtFormat` and `gmtZeroFormat` in your locale. See [Time Zones and City names](translation/time-zones-and-city-names)
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)
112
+
For zone `Etc/Unknown`, the exemplarCity name was changed in English from “Unknown City” to “Unknown Location”; other locales should update accordingly.
<!-- this is unnecessary for vetters to worry about.
99
124
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.
125
+
-->
100
126
- 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.
127
+
-**Note that some currency units may only be alphabetic at the start or end, such as CA$ or $CA.
128
+
This pattern will be used if an alphabetic character would end up being adjacent to a number in the regular pattern.
129
+
So suppose that the regular pattern is "¤#,##0" and this pattern is "¤ #,##0":
130
+
$CA would use this pattern ("$CA 123"), but CA$ would just use the regular pattern to get "CA$123".**
101
131
- 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
132
103
133
For more information see [Number and currency patterns](/translation/number-currency-formats/number-and-currency-patterns).
104
134
105
135
#### Rational formats
106
136
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)
137
+
These describe the formatting of rational fractions such as ¾ or combinations of integers and fractions such as 5½.
Here are the the English values and a short description of their purpose; for more information see (TBD):
140
+
Here are the the English values and a short description of their purpose:
110
141
-`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
142
-`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.
143
+
-`rationalFormats-integerAndRationalPattern-superSub`: “{0}{1}” - The format for combining an integer with a rational fraction using composed using the pattern above; the English pattern uses U+2060 WORD JOINER, a zero-width no-break space.
113
144
-`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
145
146
+
If an integer and fraction (5½) is best expressed in your language with a space between them (5 ½),
147
+
then copy the pattern from integerAndRationalPattern to integerAndRationalPattern-superSub.
148
+
However, you **cannot** do the reverse.
149
+
Some fonts and rendering systems don't properly handle the fraction slash, and the user would see something like 51/2 (fifty-one halves).
150
+
So in that case, implementations must have the integerAndRationalPattern with a space in it to fall back on,
151
+
unless they have verified that the font / rendering system supports superscripting the numerator.
152
+
153
+
See [Rational Formatting](https://cldr.unicode.org/translation/number-currency-formats/number-and-currency-patterns#rational-formatting) for more information.
154
+
115
155
### Units
116
156
117
157
#### Rework certain concentration units
118
158
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):
159
+
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:
0 commit comments