8000 Post-47 front door (#1042) · unicode-org/message-format-wg@fda35a8 · GitHub
[go: up one dir, main page]
Skip to content

Commit fda35a8

Browse files
aphillipseemeli
aphillips
and
eemeli
authored
Post-47 front door (#1042)
* Post-47 front door Update our front-door/status page to reflect the release of MF2 as stable. * Update README.md Co-authored-by: Eemeli Aro <eemeli@mozilla.com> * Update README.md Co-authored-by: Eemeli Aro <eemeli@mozilla.com> * Apply suggestions from code review Co-authored-by: Eemeli Aro <eemeli@mozilla.com> * U 8000 pdate README.md Co-authored-by: Eemeli Aro <eemeli@mozilla.com> --------- Co-authored-by: Eemeli Aro <eemeli@mozilla.com>
1 parent 6189ae0 commit fda35a8

File tree

1 file changed

+27
-45
lines changed

1 file changed

+27
-45
lines changed

‎README.md

Lines changed: 27 additions & 45 deletions
Original file line numberDiff line numberDiff line change
@@ -4,63 +4,45 @@ Welcome to the home page for the MessageFormat Working Group, a subgroup of the
44

55
## Charter
66

7-
The MessageFormat Working Group (MFWG) is tasked with developing an industry standard
8-
for the representation of localizable message strings to be a successor to
9-
[ICU MessageFormat](https://unicode-org.github.io/icu/userguide/format_parse/messages/).
10-
MFWG will recommend how to remove redundancies,
11-
make the syntax more usable,
12-
and support more complex features, such as gender, inflections, and speech.
13-
MFWG will also consider the integration of the new standard with programming environments,
14-
including, but not limited to, ICU, DOM, and ECMAScript, and with localization platform interchange.
15-
The output of MFWG will be a specification for the new syntax.
16-
17-
- [Why ICU MessageFormat Needs a Successor](docs/why_mf_next.md)
18-
- [Goals and Non-Goals](docs/goals.md)
19-
20-
## MessageFormat 2 Final Candidate
21-
22-
The [MessageFormat 2 specification](./spec/) is a new part of
7+
The MessageFormat Working Group (MFWG) is tasked with developing and supporting an industry standard
8+
for the representation of localizable message strings.
9+
MessageFormat is designed to support software developers, translators, and end users with fluent messages
10+
and locally-adapted presentation for data values
11+
while providing a framework for increasingly complex features, such as gender, inflections, and speech.
12+
Our goal is to provide an interoperable syntax, message data model, and associated processing that is
13+
capable of being adopted by any presentation framework or programming environement.
14+
15+
## MessageFormat 2
16+
17+
The [MessageFormat 2 specification](./spec/) has been approved by the CLDR Technical Committee
18+
and is now a stable part of
2319
the [LDML](https://www.unicode.org/reports/tr35/) specification.
24-
MessageFormat 2 has been approved by the CLDR Technical Committee
25-
to be issued as a "Final Candidate".
26-
This means that the stability policy is not in effect and feedback from
27-
users and implementers might result in changes to the syntax, data model,
28-
functions, or other normative aspects of MessageFormat 2.
29-
Such changes are expected to be minor and, to the extent possible,
30-
to be compatible with what is defined in the Final Candidate specification.
20+
It is now recommended for implementation and adoption.
21+
22+
Some _default functions_ and items in the `u:` namespace are still in Draft status.
23+
Feedback from users and implementers might result in changes to these capabilities.
3124

3225
The MessageFormat Working Group and CLDR Technical Committee welcome any and all feedback,
3326
including bugs reports,
3427
implementation reports,
3528
success stories,
3629
feature requests,
3730
requests for clarification,
38-
or anything that would be helpful in stabilizing the specification and
31+
or anything that would be helpful in supporting or enhancing the specification and
3932
promoting widespread adoption.
4033

41-
The MFWG specifically requests feedback on the following issues:
42-
- How to perform non-integer exact number selection [#675](https://github.com/unicode-org/message-format-wg/issues/675)
43-
- Whether omitting the `*` variant key should be permitted [#603](https://github.com/unicode-org/message-format-wg/issues/603)
44-
- Whether there should be normative requirements for markup handling [#586](https://github.com/unicode-org/message-format-wg/issues/586)
45-
- Whether the delimiters used for literals and patterns were chosen correctly [#602](https://github.com/unicode-org/message-format-wg/issues/602)
46-
47-
## Normative Changes during the Final Candidate period
48-
49-
The MessageFormat Working Group continues to address feedback
50-
and develop portions of the specification not completed for the LDML 46.1 Final Candidate release.
51-
The `main` branch of this repository contains changes implemented since the specification was released.
52-
53-
Implementers should be aware of the following normative changes during the v46.1 final candidate review period.
54-
See the [commit history](https://github.com/unicode-org/message-format-wg/commits)
55-
after 2024-11-20 for a list of all commits (including non-normative changes).
56-
57-
In addition to the above, the test suite has been modified and updated.
58-
5934
## Sharing Feedback
6035

61-
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+)
36+
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+)
6237

63-
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.
38+
We invite feedback about implementation difficulties,
39+
proposed functions or options
40+
real-life use-cases,
41+
requirements for future work,
42+
tooling,
43+
runtime APIs,
44+
localization workflows,
45+
and other topics.
6446

6547
- General questions and thoughts → [post a discussion thread](https://github.com/unicode-org/message-format-wg/discussions).
6648
- 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:
8466

8567
### Copyright & Licenses
8668

87-
Copyright © 2019-2024 Unicode, Inc. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. in the United States and other countries.
69+
Copyright © 2019-2025 Unicode, Inc. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. in the United States and other countries.
8870

8971
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.
9072

0 commit comments

Comments
 (0)
0