Excellent.

See also which is about date-time combining patterns for intervalFormats that combine a specific date with a time range, e.g. "January 19, 2022" and "08:30-10:00". In that case we would not want to use “{1} 'at' {0}” as we currently have in English. For that we were also going to add another set of 4 patterns. But that is likely similar to the relative-and-absolute pattern requested above, basically a pattern with separator but no grammatical joining context.

We need to have a single design that handles all of these. And note that the current default is actually the “event” style, with the grammatical context. I think that is wrong, the default should be without context.

Here is the structure that we currently have for English:

So here is what I propose, with the default data changing to the non-event style (time of day), and the “event” style moving to an alt variant; for medium and short there is no difference in English, so they fall back:

If we need more variants we can add them in the future. If this seems OK, I can take this ticket to do this, and then will resolve as a dup of this one.

Needs an example with hover preview

How about:

<dateTimeFormats>

…

<relativeAndAbsolutePattern>{0}, {1}</…>

<dateTimeEventPattern>{0} at {1}</…>

I think that would also be a useful addition.