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
Spun off from #108 and #119 . options.skeleton was discussed in #108, but I don't find any new bug filed. So, I'm doing it. If it's already filed and worked on, I'm sorry and a pointer to the existing bug would be appreciated.
In Ecma 402 v1 back in early 2010's, there's a debate over verbose options ('month': short, 'month': 'numeric' , etc) vs LDML-style format specifiers (M, MM, MMM, MMMM). Verbose options were what's agreed upon.
Verbose options have some advantages, but they also have some cons; they're too verbose and sometimes hard to remember - devtools can help for sure. As shown in #119, it's hard to come up with succinct names for plethora of LDML format specifiers [1] (field and values. especially values for timezone display format ).
options.skeleton - there's a big support for this option. It allows for "more advanced things", it is "almost ubiquitous for any internationalization platform".
[1] I'm not necessarily saying that we have to support every single one of them.
The text was updated successfully, but these errors were encountered:
Spun off from #108 and #119 . options.skeleton was discussed in #108, but I don't find any new bug filed. So, I'm doing it. If it's already filed and worked on, I'm sorry and a pointer to the existing bug would be appreciated.
In Ecma 402 v1 back in early 2010's, there's a debate over verbose options ('month': short, 'month': 'numeric' , etc) vs LDML-style format specifiers (M, MM, MMM, MMMM). Verbose options were what's agreed upon.
Verbose options have some advantages, but they also have some cons; they're too verbose and sometimes hard to remember - devtools can help for sure. As shown in #119, it's hard to come up with succinct names for plethora of LDML format specifiers [1] (field and values. especially values for timezone display format ).
Quoting @rxaviers 's summary in #108,
[1] I'm not necessarily saying that we have to support every single one of them.
The text was updated successfully, but these errors were encountered: