Skip to content

Conversation

eemeli
Copy link
Contributor

@eemeli eemeli commented Aug 11, 2025

CLDR-18879

  • This PR completes the ticket.

The tooling used to map the MessageFormat WG's editable copy of the spec to this form was recently updated in unicode-org/message-format-wg#1096, and a rendered version of the editable spec is now available at https://unicode-org.github.io/message-format-wg/.

That currently corresponds to this PR, but may change if and as the WG makes further changes. No further changes are planned for inclusion in LDML 48.

ALLOW_MANY_COMMITS=true

eemeli added 2 commits August 14, 2025 19:00
- Move Option Resolution up one level in hierarchy, to more clearly apply to Markup Resolution as well as Function Resolution.
- Move Pattern Selection Examples to the Appendices.
- Make section titles unique, adding _numeric operand_ as a term.
- Fix whitespace.
Changes to REQUIRED parts of the specification:

- Require prioritising syntax & data model errors (unicode-org#1011)
- Make the Default Bidi Strategy required and default (unicode-org#1066)
- Rename `:math` as `:offset` and publish it as Stable (unicode-org#1073)

Changes to OPTIONAL or Draft parts of the specification:

- Rebrand the format more clearly as "Unicode MessageFormat" (unicode-org#1064)
- Refactor the pattern selection definition without changing its meaning (unicode-org#1080)
- Update the `:datetime`, `:date`, and `:time` functions to build on semantic skeletons (unicode-org#1078, unicode-org#1083)
- Add `:percent` as a new Draft function (unicode-org#1094)
@eemeli eemeli force-pushed the update-messageformat branch from e220735 to 1e2f444 Compare August 14, 2025 16:08
@jira-pull-request-webhook
Copy link

Notice: the branch changed across the force-push!

  • docs/ldml/tr35-messageFormat.md is different

View Diff Across Force-Push

~ Your Friendly Jira-GitHub PR Checker Bot

Copy link
Member

@srl295 srl295 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no production or generation issues i can see.

@srl295
Copy link
Member

srl295 commented Sep 10, 2025

no production or generation issues i can see.

As discussed during the CLDR TC meeting, the commit message numbers could be better unicode-org/message-format-wg#1096 or the full PR URL instead of just #1096

@srl295 srl295 assigned srl295 and unassigned eemeli Sep 10, 2025
@srl295 srl295 merged commit 9a9f800 into unicode-org:main Sep 10, 2025
11 checks passed
@eemeli eemeli deleted the update-messageformat branch September 10, 2025 16:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants