diff --git a/README.md b/README.md index 50d58c00f2..8b835d2fd6 100644 --- a/README.md +++ b/README.md @@ -4,30 +4,23 @@ Welcome to the home page for the MessageFormat Working Group, a subgroup of the ## Charter -The MessageFormat Working Group (MFWG) is tasked with developing an industry standard -for the representation of localizable message strings to be a successor to -[ICU MessageFormat](https://unicode-org.github.io/icu/userguide/format_parse/messages/). -MFWG will recommend how to remove redundancies, -make the syntax more usable, -and support more complex features, such as gender, inflections, and speech. -MFWG will also consider the integration of the new standard with programming environments, -including, but not limited to, ICU, DOM, and ECMAScript, and with localization platform interchange. -The output of MFWG will be a specification for the new syntax. - -- [Why ICU MessageFormat Needs a Successor](docs/why_mf_next.md) -- [Goals and Non-Goals](docs/goals.md) - -## MessageFormat 2 Final Candidate - -The [MessageFormat 2 specification](./spec/) is a new part of +The MessageFormat Working Group (MFWG) is tasked with developing and supporting an industry standard +for the representation of localizable message strings. +MessageFormat is designed to support software developers, translators, and end users with fluent messages +and locally-adapted presentation for data values +while providing a framework for increasingly complex features, such as gender, inflections, and speech. +Our goal is to provide an interoperable syntax, message data model, and associated processing that is +capable of being adopted by any presentation framework or programming environement. + +## MessageFormat 2 + +The [MessageFormat 2 specification](./spec/) has been approved by the CLDR Technical Committee +and is now a stable part of the [LDML](https://www.unicode.org/reports/tr35/) specification. -MessageFormat 2 has been approved by the CLDR Technical Committee -to be issued as a "Final Candidate". -This means that the stability policy is not in effect and feedback from -users and implementers might result in changes to the syntax, data model, -functions, or other normative aspects of MessageFormat 2. -Such changes are expected to be minor and, to the extent possible, -to be compatible with what is defined in the Final Candidate specification. +It is now recommended for implementation and adoption. + +Some _default functions_ and items in the `u:` namespace are still in Draft status. +Feedback from users and implementers might result in changes to these capabilities. The MessageFormat Working Group and CLDR Technical Committee welcome any and all feedback, including bugs reports, @@ -35,32 +28,21 @@ implementation reports, success stories, feature requests, requests for clarification, -or anything that would be helpful in stabilizing the specification and +or anything that would be helpful in supporting or enhancing the specification and promoting widespread adoption. -The MFWG specifically requests feedback on the following issues: -- How to perform non-integer exact number selection [#675](https://github.com/unicode-org/message-format-wg/issues/675) -- Whether omitting the `*` variant key should be permitted [#603](https://github.com/unicode-org/message-format-wg/issues/603) -- Whether there should be normative requirements for markup handling [#586](https://github.com/unicode-org/message-format-wg/issues/586) -- Whether the delimiters used for literals and patterns were chosen correctly [#602](https://github.com/unicode-org/message-format-wg/issues/602) - -## Normative Changes during the Final Candidate period - -The MessageFormat Working Group continues to address feedback -and develop portions of the specification not completed for the LDML 46.1 Final Candidate release. -The `main` branch of this repository contains changes implemented since the specification was released. - -Implementers should be aware of the following normative changes during the v46.1 final candidate review period. -See the [commit history](https://github.com/unicode-org/message-format-wg/commits) -after 2024-11-20 for a list of all commits (including non-normative changes). - -In addition to the above, the test suite has been modified and updated. - ## Sharing Feedback -Final Candidate Feedback: [file an issue here](https://github.com/unicode-org/message-format-wg/issues/new?labels=Preview-Feedback&projects=&template=tech-preview-feedback.md&title=%5BFEEDBACK%5D+) +Do you have feedback on the specification or any of its elements? [file an issue here](https://github.com/unicode-org/message-format-wg/issues/new?labels=Preview-Feedback&projects=&template=tech-preview-feedback.md&title=%5BFEEDBACK%5D+) -We invite feedback about the current syntax draft, as well as the real-life use-cases, requirements, tooling, runtime APIs, localization workflows, and other topics. +We invite feedback about implementation difficulties, +proposed functions or options +real-life use-cases, +requirements for future work, +tooling, +runtime APIs, +localization workflows, +and other topics. - General questions and thoughts → [post a discussion thread](https://github.com/unicode-org/message-format-wg/discussions). - Actionable feedback (bugs, feature requests) → [file a new issue](https://github.com/unicode-org/message-format-wg/issues). @@ -84,7 +66,7 @@ To contribute to this work, in addition to the above: ### Copyright & Licenses -Copyright © 2019-2024 Unicode, Inc. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. in the United States and other countries. +Copyright © 2019-2025 Unicode, Inc. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. in the United States and other countries. A CLA is required to contribute to this project - please refer to the [CONTRIBUTING.md](./CONTRIBUTING.md) file (or start a Pull Request) for more information.