Merge branch 'main' into u-options

Author: eemeli

CONTRIBUTING.md

@@ -1,13 +1,6 @@
 # Contributing to this project
 
-## Joining the Working Group
-
-We are looking for participation from software developers, localization engineers and others with experience
-in Internationalization (I18N) and Localization (L10N). If you wish to contribute to this work, please review
-the information on the Contributor License Agreement below. In addition, you should:
-
-1. Apply to join our [mailing list](https://groups.google.com/a/chromium.org/forum/#!forum/message-format-wg)
-2. Watch this repository (use the "Watch" button in the upper right corner)
+To join this Working Group, please read the information in the [README.md](./README.md) as well as the Contributor License Agreement information just below:
 
 <!-- boilerplate follows - do not edit -->
 

README.md

@@ -76,7 +76,8 @@ Functions can optionally take _options_:
 Messages can use a _selector_ to choose between different _variants_,
 which correspond to the grammatical (or other) requirements of the language:
 
-    .match {$count :integer}
+    .input {$count :integer}
+    .match $count
     0   {{You have no notifications.}}
     one {{You have {$count} notification.}}
     *   {{You have {$count} notifications.}}
@@ -105,6 +106,23 @@ The `main` branch of this repository contains changes implemented since the tech
 Implementers should be aware of the following normative changes during the tech preview period.
 See the [commit history](https://github.com/unicode-org/message-format-wg/commits) 
 after 2024-04-13 for a list of all commits (including non-normative changes).
+- [#885](https://github.com/unicode-org/message-format-wg/issues/885) Address equality of `name` and `literal` values, including requiring keys to use NFC
+- [#884](https://github.com/unicode-org/message-format-wg/issues/884) Add support for bidirectional isolates and strong marks in syntax and address UAX31/UTS55 requirements
+- [#883](https://github.com/unicode-org/message-format-wg/issues/883) Remove forward-compatibility promise and all reserved/private syntax.
+- [#882](https://github.com/unicode-org/message-format-wg/issues/882) Specify `bad-option` error for bad digit size options in `:number` and `:integer` functions
+- [#878](https://github.com/unicode-org/message-format-wg/issues/878) Clarify "rule" selection in `:number` and `:integer` functions
+- [#877](https://github.com/unicode-org/message-format-wg/issues/877) Match on variables instead of expressions. 
+- [#854](https://github.com/unicode-org/message-format-wg/issues/854) Allow whitespace at complex message start
+- [#853](https://github.com/unicode-org/message-format-wg/issues/853) Add a "duplicate-variant" error
+- [#845](https://github.com/unicode-org/message-format-wg/issues/845) Define "attributes" feature
+- [#834](https://github.com/unicode-org/message-format-wg/issues/834) Modify the stability policy (not currently in effect due to Tech Preview)
+- [#816](https://github.com/unicode-org/message-format-wg/issues/816) Refine error handling
+- [#815](https://github.com/unicode-org/message-format-wg/issues/815) Removed machine-readable function registry as a deliverable
+- [#813](https://github.com/unicode-org/message-format-wg/issues/813) Change default of `:date` and `:datetime` date formatting from `short` to `medium`
+- [#812](https://github.com/unicode-org/message-format-wg/issues/812) Allow trailing whitespace for complex messages
+- [#793](https://github.com/unicode-org/message-format-wg/issues/793) Recommend the use of escapes only when necessary
+- [#775](https://github.com/unicode-org/message-format-wg/issues/775) Add formal definitions for variable, external variable, and local variable
+- [#774](https://github.com/unicode-org/message-format-wg/issues/774) Refactor errors, adding Message Function Errors
 - [#771](https://github.com/unicode-org/message-format-wg/issues/771) Remove inappropriate normative statement from errors.md
 - [#767](https://github.com/unicode-org/message-format-wg/issues/767) Add a test schema and
   [#778](https://github.com/unicode-org/message-format-wg/issues/778) validate tests against it
@@ -113,7 +131,9 @@ after 2024-04-13 for a list of all commits (including non-normative changes).
 - [#769](https://github.com/unicode-org/message-format-wg/issues/769) Add `:test:function`,
   `:test:select` and `:test:format` functions for implementation testing
 - [#743](https://github.com/unicode-org/message-format-wg/issues/743) Collapse all escape sequence rules into one (affects the ABNF)
-- _more to be added as they are merged_
+
+In addition to the above, the test suite is significantly modified and updated.
+
 
 ## Implementations
 
@@ -137,18 +157,27 @@ We invite feedback about the current syntax draft, as well as the real-life use-
 - 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).
 
-## Participation
+## Participation / Joining the Working Group
+
+We are looking for participation from software developers, localization engineers and others with experience
+in Internationalization (I18N) and Localization (L10N). 
+If you wish to contribute to this work, please review the information about the Contributor License Agreement below. 
 
-To join in:
+To follow this work:
+1. Apply to join our [mailing list](https://groups.google.com/a/chromium.org/forum/#!forum/message-format-wg)
+2. Watch this repository (use the "Watch" button in the upper right corner)
 
-1. Review [CONTRIBUTING.md](./CONTRIBUTING.md)
-2. Apply to join our [mailing list](https://groups.google.com/a/chromium.org/forum/#!forum/message-format-wg)
-3. Watch this repository (use the "Watch" button in the upper right corner)
+To contribute to this work, in addition to the above:
+1. Each individual MUST have a copy of the CLA on file. See below.
+2. Individuals who are employees of Unicode Member organizations SHOULD contact their member representative.
+   Individuals who are not employees of Unicode Member organizations MUST contact the chair to request Invited Expert status.
+   Employees of Unicode Member organizations MAY also apply for Invited Expert status,
+   subject to approval from their member representative.
 
 ### 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.
 
-The project is released under [LICENSE](./LICENSE).
-
 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.
+
+The contents of this repository are governed by the Unicode [Terms of Use](https://www.unicode.org/copyright.html) and are released under [LICENSE](./LICENSE).