Long localized GMT format (e.g., GMT-08:00) "shortGeneric" Short localized GMT format (e.g., GMT-8) "longOffset" Short localized form (e.g.: PST, GMT-8) "shortOffset" Long localized form (e.g., Pacific Standard Time, Nordamerikanische Westküsten-Normalzeit) "short" The localized representation of the time zone name. The number of digits used to represent fractions of a second (any additional digits are truncated). Possible values are "numeric" and "2-digit". Many locales use the same string irrespective of the width specified. Note: This option only has an effect if a 12-hour clock ( hourCycle: "h12" or hourCycle: "h11") is used. The formatting style used for day periods like "in the morning", "am", "noon", "n" etc. Two months may have the same narrow style for some locales (e.g. Two weekdays may have the same narrow style for some locales (e.g. Implementations may also recognize the time zone names of the IANA time zone database, such as "Asia/Shanghai", "Asia/Kolkata", "America/New_York". The only value implementations must recognize is "UTC" the default is the runtime's default time zone. This option can also be set through the hc Unicode extension key if both are provided, this options property takes precedence. It sets hourCycle to "h11" or "h12" when true, and "h23" or "h24" when false, the exact choice depending on the locale - for example, if the locale most prefers "h23" but hour12 is true, then the final hour cycle is "h11". This option overrides the hc locale extension tag and/or the hourCycle option in case both are present. Possible values are true and false the default is locale dependent. Whether to use 12-hour time (as opposed to 24-hour time). This option can also be set through the nu Unicode extension key if both are provided, this options property takes precedence. For a list of supported numbering system types, see (). The numbering system to use for number formatting, such as "arab", "hans", "mathsans", and so on. This option can also be set through the ca Unicode extension key if both are provided, this options property takes precedence. For a list of supported calendar types, see (). The calendar to use, such as "chinese", "gregory", "persian", and so on. For information about this option, see Locale identification and negotiation. Possible values are "lookup" and "best fit" the default is "best fit". For ease of reading, the property list is broken into sections based on their purposes, including locale options, date-time component options, and style shortcuts. When both are set, the options property takes precedence. These keys can also be set with options (as listed below). The following Unicode extension key is allowed: nu For the general form and interpretation of the locales argument, see the parameter description on the Intl main page.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |