11 | The CanonicalCodeForDisplayNames abstract operation is called with arguments _type_, _code_. It verifies that the _code_ argument represents a well-formed code according to the _type_ argument and returns the case-regularized form of the _code_. The algorithm refers to UTS 35's Unicode Language and Locale Identifiers grammar. The following steps are taken: 12 |
13 |45 | 46 | The IsValidDateTimeFieldCode abstract operation is called with argument _field_. It verifies that the _field_ argument represents a valid date time field code. The following steps are taken: 47 | 48 |
49 || Code | 60 |Description | 61 |
|---|---|
| `"era"` | 65 |The field indicating the era, e.g. AD or BC in the Gregorian (Julian) calendar. | 66 |
| `"year"` | 69 |The field indicating the year. | 70 |
| `"quarter"` | 73 |The field indicating the quarter, e.g. Q2, 2nd quarter, etc. | 74 |
| `"month"` | 77 |The field indicating the month, e.g. Sep, September, etc. | 78 |
| `"weekOfYear"` | 81 |The field indicating the week number within the current year. | 82 |
| `"weekday"` | 85 |The field indicating the day of week, e.g. Tue, Tuesday, etc. | 86 |
| `"day"` | 89 |The field indicating the day in month. | 90 |
| `"dayPeriod"` | 93 |The field indicating the day period, either am/pm marker or others, e.g. noon, evening. | 94 |
| `"hour"` | 97 |The field indicating the hour. | 98 |
| `"minute"` | 101 |The field indicating the minute. | 102 |
| `"second"` | 105 |The field indicating the second. | 106 |
| `"timeZoneName"` | 109 |The field indicating the time zone name, e.g. PDT, Pacific Daylight Time, etc. | 110 |
120 | The DisplayNames constructor is a standard built-in property of the Intl object.
121 | 122 |126 | When the *Intl.DisplayNames* function is called with arguments _locales_ and _options_, the following steps are taken: 127 |
128 | 129 |170 | The Intl.DisplayNames constructor has the following properties: 171 |
172 | 173 |177 | The value of *Intl.DisplayNames.prototype* is *%DisplayNamesPrototype%*. 178 |
179 |180 | This property has the attributes { [[Writable]]: *false*, [[Enumerable]]: *false*, [[Configurable]]: *false* }. 181 |
182 |188 | When the *supportedLocalesOf* method of *%DisplayNames%* is called, the following steps are taken: 189 |
190 | 191 |
202 | The value of the [[AvailableLocales]] internal slot is implementation defined within the constraints described in
206 | The value of the [[RelevantExtensionKeys]] internal slot is « ». 207 |
208 | 209 |
210 | The value of the [[LocaleData]] internal slot is implementation defined within the constraints described in
236 | The Intl.DisplayNames prototype object, referred to as *%DisplayNamesPrototype%*, is itself an ordinary object. It is not a Intl.DisplayNames instance, does not have an [[InitializedDisplayNames]] internal slot or any of the other internal slots of Intl.DisplayNames instance objects. 237 |
238 | 239 |243 | The initial value of *Intl.DisplayNames.prototype.constructor* is the intrinsic object *%DisplayNames%*. 244 |
245 |251 | The initial value of the @@toStringTag property is the string value `"Intl.DisplayNames"`. 252 |
253 |254 | This property has the attributes { [[Writable]]: *false*, [[Enumerable]]: *false*, [[Configurable]]: *true* }. 255 |
256 |262 | When the *Intl.DisplayNames.prototype.of* is called with an argument _code_, the following steps are taken: 263 |
264 | 265 |283 | This function provides access to the locale and options computed during initialization of the object. 284 |
285 | 286 || Internal Slot | 305 |Property | 306 |
|---|---|
| [[Locale]] | 310 |`"locale"` | 311 |
| [[Style]] | 314 |`"style"` | 315 |
| [[Type]] | 318 |`"type"` | 319 |
| [[Fallback]] | 322 |`"fallback"` | 323 |
| [[LanguageDisplay]] | 326 |`"languageDisplay"` | 327 |
337 | Intl.DisplayNames instances are ordinary objects that inherit properties from %DisplayNamesPrototype%. 338 |
339 | 340 |341 | Intl.DisplayNames instances have an [[InitializedDisplayNames]] internal slot. 342 |
343 | 344 |345 | Intl.DisplayNames instances also have several internal slots that are computed by the constructor: 346 |
347 | 348 |This proposal enhances the Intl.DisplayNames API and cover more display names for weekday, month, time zone, unit, calendar, numbering system, etc. 2249 | See the README for more context.
2250 |2262 | The CanonicalCodeForDisplayNames abstract operation is called with arguments type, code. It verifies that the code argument represents a well-formed code according to the type argument and returns the case-regularized form of the code. The algorithm refers to UTS 35's Unicode Language and Locale Identifiers grammar. The following steps are taken: 2263 |
2264 |"language", thenunicode_language_id production, throw a "region", thenunicode_region_subtag production, throw a "script", thenunicode_script_subtag production, throw a "calendar", thentype nonterminal, throw a "dateTimeField", then"currency".2271 | 2272 | The IsValidDateTimeFieldCode abstract operation is called with argument field. It verifies that the field argument represents a valid date time field code. The following steps are taken: 2273 | 2274 |
2275 || Code | 2283 |Description | 2284 |
|---|---|
"era" |
2288 | The field indicating the era, e.g. AD or BC in the Gregorian (Julian) calendar. | 2289 |
"year" |
2292 | The field indicating the year. | 2293 |
"quarter" |
2296 | The field indicating the quarter, e.g. Q2, 2nd quarter, etc. | 2297 |
"month" |
2300 | The field indicating the month, e.g. Sep, September, etc. | 2301 |
"weekOfYear" |
2304 | The field indicating the week number within the current year. | 2305 |
"weekday" |
2308 | The field indicating the day of week, e.g. Tue, Tuesday, etc. | 2309 |
"day" |
2312 | The field indicating the day in month. | 2313 |
"dayPeriod" |
2316 | The field indicating the day period, either am/pm marker or others, e.g. noon, evening. | 2317 |
"hour" |
2320 | The field indicating the hour. | 2321 |
"minute" |
2324 | The field indicating the minute. | 2325 |
"second" |
2328 | The field indicating the second. | 2329 |
"timeZoneName" |
2332 | The field indicating the time zone name, e.g. PDT, Pacific Daylight Time, etc. | 2333 |
2343 | The DisplayNames
2349 | When the
"%DisplayNamesPrototype%", « [[InitializedDisplayNames]], [[Locale]], [[Style]], [[Type]], [[Fallback]], [[LanguageDisplay]], [[Fields]] »)."localeMatcher", "string", « "lookup", "best fit" », "best fit")."style", "string", « "narrow", "short", "long" », "long")."type", "string", « "language", "region", "script", "currency" , "calendar", "dateTimeField"», "fallback", "string", « "code", "none" », "code")."languageDisplay", "string", « "dialect", "standard" », "dialect")."language", then
2360 | The Intl.DisplayNames
2367 | The value of
2370 | This property has the attributes { [[Writable]]:
2378 | When the
2388 | The value of the [[AvailableLocales]] internal slot is implementation defined within the constraints described in
2392 | The value of the [[RelevantExtensionKeys]] internal slot is « ». 2393 |
2394 | 2395 |
2396 | The value of the [[LocaleData]] internal slot is implementation defined within the constraints described in
"language", "region", "script", "currency", "calendar", and "dateTimeField"."language" must be a "dialect" and "standard"."language" should contain Records which must have fields with the names of one of the valid display name styles: "narrow", "short", and "long"."language", "region", "script", "currency", "calendar", and "dateTimeField" must be a "narrow", "short", and "long"."language" should contain Records, with keys corresponding to language codes according to unicode_language_id production. The value of these fields must be string values."region" should contain Records, with keys corresponding to region codes. The value of these fields must be string values."script" should contain Records, with keys corresponding to script codes. The value of these fields must be string values."currency" should contain Records, with keys corresponding to currency codes. The value of these fields must be string values."calendar" should contain Records, with keys corresponding to a String value with the type given in Unicode Technical Standard 35 for the calendar used for formatting. The value of these fields must be string values."dateTimeField" should contain Records, with keys corresponding to codes listed in
2422 | The Intl.DisplayNames prototype object, referred to as
2429 | The initial value of
2437 | The initial value of the @@toStringTag property is the string value "Intl.DisplayNames".
2438 |
2440 | This property has the attributes { [[Writable]]:
2448 | When the
"code", return code.2458 | This function provides access to the locale and options computed during initialization of the object. 2459 |
2460 | 2461 || Internal Slot | 2469 |Property | 2470 |
|---|---|
| [[Locale]] | 2474 |"locale" |
2475 |
| [[Style]] | 2478 |"style" |
2479 |
| [[Type]] | 2482 |"type" |
2483 |
| [[Fallback]] | 2486 |"fallback" |
2487 |
| [[LanguageDisplay]] | 2490 |"languageDisplay" |
2491 |
2501 | Intl.DisplayNames instances are ordinary objects that inherit properties from %DisplayNamesPrototype%. 2502 |
2503 | 2504 |2505 | Intl.DisplayNames instances have an [[InitializedDisplayNames]] internal slot. 2506 |
2507 | 2508 |
2509 | Intl.DisplayNames instances also have several internal slots that are computed by the
"narrow", "short", or "long", identifying the display names style used."language", "region", "script", "currency", "calendar", or "dateTimeField", identifying the type of the display names requested."code", or "none", identifying the fallback return when the system does not have the requested display name."dialect" or "standard", identifying the language display kind. It is only used when [[Type]] has the value "language".© 2021 Google, Ecma International
2527 | 2528 |All Software contained in this document ("Software") is protected by copyright and is being made available under the "BSD License", included below. This Software may be subject to third party rights (rights from parties other than Ecma International), including patent rights, and no licenses under such third party rights are granted under this license even if the third party concerned is a member of Ecma International. SEE THE ECMA CODE OF CONDUCT IN PATENT MATTERS AVAILABLE AT https://ecma-international.org/memento/codeofconduct.htm FOR INFORMATION REGARDING THE LICENSING OF PATENT CLAIMS THAT ARE REQUIRED TO IMPLEMENT ECMA INTERNATIONAL STANDARDS.
2530 | 2531 |Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
2532 | 2533 |THIS SOFTWARE IS PROVIDED BY THE ECMA INTERNATIONAL "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL ECMA INTERNATIONAL BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
2540 | 2541 |7 | title: Intl.DisplayNames v2 Proposal 8 | stage: 3 9 | location: https://tc39.es/intl-displaynames-v2/ 10 | copyright: true 11 | contributors: Google, Ecma International 12 |13 | 14 |
This proposal enhances the Intl.DisplayNames API and cover more display names for weekday, month, time zone, unit, calendar, numbering system, etc. 18 | See the README for more context.
19 |