[AGENDA] MessageFormat 2025-02-24

4 views
Skip to first unread message

Addison Phillips

unread,
Feb 21, 2025, 6:56:57 PMFeb 21
to Message Format Working Group

All,

The agenda for the 2025-02-24 call has been updated.

You can find it here:

https://docs.google.com/document/d/1y4jow5E7tzurD7sMmemH79x8fD5dgZdCBx7eD5bxjaY/edit

This is a regular teleconference.

The focus of this call will be approving the final version of the LDML47 release of the specification. A lot of work took place over the past week. We'll review that work and look at the draft spec. We'll also review open issues against this release to ensure that we are comfortable in punting them down the road.

Behold the agenda:

Topic: PR Review

Timeboxed review of items ready for merge.


PR

Description

Recommendation

#1011

Require prioritizing syntax and data model errors

Defer to 48


Topic: LDML47 Stable Release

After a flurry of activity, the final release version of the specification was created. Let’s briefly review the changes that were made using fast-tracking and other strategies. In this call, we are likely to tag the release.


Topic: LDML47 Issues

Some issues have LDML47 labels.

Topic: Issue review

We will probably not get to all of the items in the table this week. Most are queued up for discussion in the 3 March 2025 call.

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

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

  • 6 are tagged for 47

  • 20 are tagged for 48

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

  • 5 are tagged “Future”

  • 17 are Preview-Feedback

  • 6 are resolve-candidate and proposed for close.

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

  • 0 are ballots


Issue

Description

Recommendation

724

Rationalize name-char

Agenda+, Resolve-candidate (#1008)

#866

CLDR semantic datetime skeleton spec is nearly ready and MF2 should use it

Agenda+, Discuss

#1033

Stability policy conflict with allowing all identifiers

LDML47, Discuss

#993

Update test schema to make expErrors “array” only

Discuss, resolve-candidate

#997, #1004

spec/bidi “overreaching”, bidi test cases

Discuss

#1005

Test checking the markup arguments

Discuss




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

Internationalization is not a feature.
It is an architecture.
Reply all
Reply to author
Forward
0 new messages