Nightly Changelog: 8.1.2-b202012011
Platform
240: UI updates for tag permissions editor
Layout in the security permissions panel of Tag Editor now properly resizes with the parent frame.
1186: Error âCannot add a tag at this locationâ when Canceling out from the New Folder popup
Cancelling a âNew Folderâ action in the Tag Browser no longer displays an error.
Visualization
250: Numeric Entry Field: needs to be made locale aware when it comes to format strings
With this first pass at adding locales to the Numeric Entry Field, the following locales are now supported (shown with the locale key that will map to that set of rules):
Bulgarian --> bg, bg-BG
Chinese (Simplified Chinese rules, but weâre bundling everything together. Can be broken out in the future.) --> chs, zh, zh-CN, zh-HK, zh-TW
Czech --> cs, cs-CZ
Danish --> da, da-DK
German (Germany, Austria, Luxembourg, Belgium) --> de, de-DE, de-LB
German (Switzerland) --> de-CH
Australian --> en-AU
English (USA) --> en, en-US
English (UK) --> en-GB
English (South African) --> en-ZA
Spanish (general and Mexico) --> es, es-MX
Spanish (Spain) --> es-ES
Estonian --> et, et-ET
Finnish --> fi, fi-FI
French --> fr, fr-FR
French (Canadian) --> fr-CA
French (different variant) --> fr-CH
Hungarian --> hu, hu-HU
Italian --> it, it-IT
Japanese --> ja, ja-JP
Latvian --> lv, lv-LV
Dutch --> nl, nl-NL
Dutch (Belgium) --> nl-BE
Norweigan (Norway, Norwegian BokmÄl, Norwegian Nynorsk. Can be broken out in the future.) --> no, no-NO, no-NB, no-NN
Polish --> pl, pl-PL
Portuguese --> pt, pt-PT
Portuguese (Brazil) --> pt-BR
Ukrainian --> uk, ru-UK, ru-UA
Ukrainian (Ukraine) --> uk-UA
Russian --> ru, ru-RU
Slovakian --> sk, sk-SK
Slovenian --> sl, sl-SL
Thai --> th, th-TH
Turkish --> tr, th-TR
Vietnamese --> vi, vi-VI
The default locale is en-US (English, USA), and this will also be used as a fallback locale if the user has selected/provided a locale that doesnât map to any of the above locale keys. Each set of locale rules contains a mapping of how numeric delimiters, abbreviations, ordinals, and currency symbols will be applied to the format component property of the Numeric Entry Field. The rule set for French (fr-FR) is shown here as an example:
âŠ
delimiters: {
thousands: â ',
decimal: â,â
},
abbreviations: {
thousand: âkâ,
million: âmâ,
billion: âbâ,
trillion: âtâ
},
ordinal : function (number) {
return number === 1 ? âerâ : âeâ;
},
currency: {
symbol: ââŹâ
}
âŠ
NOTE: The user will need to keep the format component property in English (USA) format as the rule mapping expects an en-US format in place first before the user-provided locale rules are applied.