-
-
Notifications
You must be signed in to change notification settings - Fork 34
Things That Need Doing
Tim Chevalier edited this page Oct 11, 2024
·
33 revisions
This page is to keep track of all of the items that are needed in order to ship MF2.0 v46.1
- Close all preview-feedback issues
- How to perform non-integer exact number selection #675, #842, #859
- Whether omitting the
*variant key should be permitted #603
- How best to define value resolution #678
- [?] Specify the handling of "resolved values"
- Specify the interaction of declarations, selectors, and variable references. #824
- Create tests
- Ensure that a complete enumeration and error types is in place
- Fix requirements for error handling #782 (ECH)
- Ensure that error requirements are defined in the specification (EAO)
- Ensure that error fallback format is define for each error state (EAO)
- Update tests to match
- Whether to relax constraints on complex message start #610
- Finish design of bidi isolation support in the message syntax #746 (APP)
- Address the handling of pattern-exterior whitespace (PEWS) with regard to UAX31 (APP)
- Write tests (See #902 and #904) (TIM)
This is no longer a required deliverable. It is an informative annex. As a result, none of the following are required to exit Tech Preview.
- Specify the Interchange Data Model
- Are namespaces separated from the name or all-one-field? (blocking)
- Ensure that there are implementations
- Update tests
- A specification for a one-to-one mapping between the data model and XLIFF
- Specify or drop the Registry Data Model #815 dropped
- Establish function set maintenance procedures #634
- Design doc done
- Add resolved value and composition sections to existing functions
- Rename/refactor registry.md to reflect function set name and design for function sets
- Categorize all functions and all options. Functions may be
[Standard]or[Optional]. Options may be[Standard]or[Optional]. - Update tests
- Whether markup should support additional spaces #650
- Whether "attribute-like" behavior is needed and what form it should take #642
- Create complete tests for syntax (TIM) #843
- Create complete tests for formatting
- Create complete tests for selection
- Create complete tests for each
[Standard]function set function.
This includes:
- format to parts (EAO) (on 2024-06-24 the WG discussed not including this)
- interchange data model (see above)
- explainer (to be used by CLDR-TC, ICU-TC, TAG, TG5)
- Review and approve the details of the stability policy as a WG
- Develop a user guide (perhaps by extending messageformat.dev - PRs can be submitted here.)
Nudge the CLA server: