Shane F. Carr

To summarize, my position currently is: - I would like to see evidence that motivates this feature - If the feature is well motivated, then the spec can stay as-is....

Thank you. I reviewed that design doc as well as the six linked PRs. Very good record-keeping. I did not, however, find justification for why _this specific expression attribute_ should...

The current design of `:unit` is not implementable with ICU4X's data design for reasons laid out in https://github.com/unicode-org/message-format-wg/issues/1006. We did not take too close of a look at `:unit` when...

> > The current design of :unit is not implementable with ICU4X's data design for reasons laid out in #1006. > > I looked at #1006 and didn't find a...

I'm spinning off the `:unit` discussion into #1079

I agree with @eemeli's comment (😃) except I think we need more discussion on > I don't think the inclusion or not of the timezone in the output merits separate...

1. `May` 2. `May 15` 3. `May 15, 10 AM` 4. `May 15, 10:01 AM` 5. `May 15, 10:01 AM CEST` Can you explain a mental model for why you...

From the MF WG meeting this week, the following design seems worth exploring: ``` # A date formatter {:datetime dateFields="YMD" } # A time formatter {:datetime timePrecision="minute" } # A...

Discussion: - Landing pages for all Unicode projects are not in a great state, but let's scope this to just the ICU4X project - Problem with publishing build artifacts (like...

TC decision: we want this for 2.0 publicity but it doesn't need to block the 2.0 _code release_