[AGENDA] MessageFormat 2025-02-17

[Addison Phillips]

All,

The agenda for the 2025-02-17 call has been updated, although please note that changes will occur through the weekend.

• Agenda: https://docs.google.com/document/d/1kTHup5wooe5o3TH78Q-Drmfzr_QOfDA-9CKRTwXkzPo/edit

The primary focus of this call will be approving the LDML47 release, which includes imposing the stability policy on most of the specification. The functions :string, :number, and :integer are proposed to be stable, while other functions (including some we previously considered candidates for stability) would still be "draft".

The ICU4X group would like us to make `option=$variable` support optional. They have written a document explaining their point of view, which we will discuss in our call. PLEASE READ THIS BEFORE THE CALL:

• https://docs.google.com/document/d/1ZJ2v8URmNuJh5E5w_CdLwk0hqOkK8pVUe44YFQuc1nY/edit

Topic: PR Review

Timeboxed review of items ready for merge.

PR	Description	Recommendation
	(none currently, expect a pour over set of fixups and one related to activating the stability policy to appear over the weekend)

Topic: LDML47 Release Finalization and Approval

The LDML47 release is upon us. The PRs necessary to release v47 will be considered in this call. We will also discuss whether/how to approve the release. ICU-TC has proposed that we stabilize the specification and the functions :string, :number, and :integer and not stabilize the other functions.

Topic: ICU4X Objections to option=$variable (#1006)

The ICU4X team wants MF2 to make supporting the assignment of option values using a variable OPTIONAL. They have produced a document explaining their position [here]. Reserving time to discuss MFWG’s reaction to this. Please read their document prior to the call.

Topic: Unquoted Literal Syntax (#724)

Mark has proposed a change to the unquoted set of chars. Let’s see if we can close this.

Topic: Issue review

https://github.com/unicode-org/message-format-wg/issues

The counts here are not stable, as I am triaging items to v48.

Currently we have 40 open (was 38 last time).

• 13 are tagged for 47

• 12 are tagged for 48

• 3 are tagged “Seek-Feedback-in-Preview”

• 6 are tagged “Future”

• 14 are Preview-Feedback

• 5 are resolve-candidate and proposed for close.

• 4 are Agenda+ and proposed for discussion (see below)

• 0 are ballots

Issue	Description	Recommendation
935	Well-formed vs. valid (particularly https://github.com/unicode-org/message-format-wg/issues/935#issuecomment-2529306693)	Moved to v48. Will not discuss in this call
724	Message Format Unquoted Literals	Discuss
#866	CLDR semantic datetime skeleton spec is nearly ready and MF2 should use it	Moved to v48. Will not discuss in this call

-- 
Addison Phillips
Chair (W3C I18N WG, MessageFormat WG)

Internationalization is not a feature.
It is an architecture.

[Shane Carr]

> The ICU4X group would like us to make `option=$variable` support optional. They have written a document explaining their point of view, which we will discuss in our call.

The position of the ICU4X Technical Committee is more nuanced than this. I do encourage everyone to read the doc.

--
You received this message because you are subscribed to the Google Groups "Message Format Working Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to message-format...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/message-format-wg/36c32f5c-5151-49dd-9f58-e8add169f6b6%40unicode.org.

[Shane Carr]

Due to a travel delay I'll be able to join the meeting starting at 10:00 PST. Thanks.