Shane F. Carr

@robertbastian agrees that we could possibly do something like this, but we should have a client so that we can build something of the right shape. I agree.

This is a big pain point in JavaScript. Here's a SO question with 461 upvotes where almost all of the answers are, "take the first char and make it upper...

Another use case to consider is https://github.com/tc39/proposal-intl-displaynames/issues/13 Different types of display names have different capitalization rules based on context. For example, you might titlecase month names in some locales but...

@markusicu What are your thoughts on putting titlecasing more front and center in JavaScript?

@everyone: if you want to see titlecasing (regardless of the exact implementation, e.g. capitalize individual words versus string toTitleCase), please :+1: the OP. There are still only 2 votes for...

In Postcard, all non-experimental keys: ``` $ cargo run --release -p icu4x-datagen -- --markers all --locales full --format blob2 --deduplication maximal -o /tmp/icu4x_maximal.postcard $ cargo run --release -p icu4x-datagen --...

I've been clear about my concern with `:date` and `:time`, stated in https://github.com/unicode-org/message-format-wg/pull/1067#issuecomment-2882873871. I apologize that I didn't attend the 2025-06-02 meeting, but my concerns were made clear well before...

An additional ergonomic issue with `:date` and `:time` is that it temps people to write messages such as `{$input :date} at {$input :time}` instead of `{$input :datetime}`.

To follow up on today's call: I'm not fully convinced with pulling out `:date` and `:time`, _but_ I would be reasonably satisfied if the Working Group published a statement explaining...

I'm okay with this, although we should have a discussion with the broader group on the option naming bikeshed.