Shane F. Carr
Shane F. Carr
@zbraniecki Do you agree with the proposed naming? - "symbols" refers to datetime field symbols, such as `M` - "names" refers to the placeholder values, such as "January" and "Jan."
We discussed this in https://github.com/tc39/ecma402/issues/777 and decided that ECMA-402 will continue rejecting underscores for the time being until we have more compelling evidence to make the change. It looks like...
I think there are a few directions we could take on this issue: 0. Document that the only difference between ECMA-402 acceptable locale identifiers and ICU4X acceptable locale identifiers is...
> sgtm Which option? 0, 1, or 2?
I don't necessarily want to spend time doing (1) if we intend to follow with (2). There isn't that much time until 2.0
Well we also want to grow into supporting other locale syntaxes such as `AR_EG@NUMBERS=LATN` which is a legacy locale syntax from ICU4C, so we probably want a BCP-47 parse function...
I would like to ask for explicit consensus on the following proposal: - Do not take action on this issue until 2.0, but we would accept a PR adding documentation...
The suggestion to merge the two originally came from https://github.com/tc39/proposal-intl-duration-format/issues/29#issuecomment-661276281. The mental model is that RelativeTimeFormat is just a duration formatter, but with an anchor time of "now". A third...
2021-06-24: - Implement `RelativeTimeFormat` in conformance with ECMA-402 - @sffc - Like #800, consider making `RelativeTimeFormat` a sub formatter of `DurationFormat` (#801) - Consider naming the class `RelativeDurationFormat` instead of...