Skip to content

Issues: unicode-org/message-format-wg

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

Stability policy should cover option values Agenda+ Requested for upcoming teleconference LDML46.1 MF2.0 Draft Candidate normative specification
#928 opened Nov 8, 2024 by aphillips
[FEEDBACK] Implementing u:dir is a little bit tricky Preview-Feedback Feedback gathered during the technical preview
#918 opened Oct 27, 2024 by eemeli
[FEEDBACK] Simpler formulation of Pattern Selection formatting Preview-Feedback Feedback gathered during the technical preview
#898 opened Oct 3, 2024 by macchiati
Add optional normative guidance on bidi/whitespace serialization Action-Item Action item assigned by the WG LDML46.1 MF2.0 Draft Candidate syntax Issues related with MF Syntax
#889 opened Sep 16, 2024 by aphillips
TC39-TG2 would like to see completion of the TG5 study Preview-Feedback Feedback gathered during the technical preview
#865 opened Aug 22, 2024 by sffc
Ask ICU-TC for feedback Action-Item Action item assigned by the WG
#864 opened Aug 22, 2024 by echeran
Update CLDR test data LDML46.1 MF2.0 Draft Candidate organizational Issues related with MF group organization and workflow resolve-candidate This issue appears to have been answered or resolved, and may be closed soon. test-suite
#856 opened Aug 8, 2024 by aphillips
Conformance with UAX #31 & UTS #55 Action-Item Action item assigned by the WG blocker-candidate The submitter thinks this might be a block for the Technology Preview normative syntax Issues related with MF Syntax
#847 opened Jul 30, 2024 by eemeli
[FEEDBACK] The re-use of :function between "annotation" and "output" positions can be a bit confusing Preview-Feedback Feedback gathered during the technical preview resolve-candidate This issue appears to have been answered or resolved, and may be closed soon.
#818 opened Jul 9, 2024 by lucacasonato
Update WG documentation to reflect change in status of default registry format materials Action-Item Action item assigned by the WG documentation Improvements or additions to documentation editorial
#817 opened Jul 9, 2024 by aphillips
Ask W3C TAG for feedback Action-Item Action item assigned by the WG LDML 47 LDML 47 Release (Stable)
#805 opened Jun 3, 2024 by aphillips
Consider adding a token grammar Future Deferred for future standardization specification
#729 opened Mar 14, 2024 by catamorphism
[FEEDBACK] Message Format Unquoted Literals Future Deferred for future standardization Preview-Feedback Feedback gathered during the technical preview resolve-candidate This issue appears to have been answered or resolved, and may be closed soon. syntax Issues related with MF Syntax
#724 opened Mar 13, 2024 by macchiati
[FEEDBACK] add :number offset option Action-Item Action item assigned by the WG LDML46.1 MF2.0 Draft Candidate Preview-Feedback Feedback gathered during the technical preview registry
#701 opened Mar 3, 2024 by macchiati
Restrict literals for :date and :time LDML46.1 MF2.0 Draft Candidate registry
#680 opened Feb 22, 2024 by eemeli
Other issues in the Registry section. registry resolve-candidate This issue appears to have been answered or resolved, and may be closed soon. Stale
#677 opened Feb 21, 2024 by macchiati
Review non-integral exact number selection algorithm blocker-candidate The submitter thinks this might be a block for the Technology Preview formatting Seek-Feedback-in-Preview Issue should be something we seek feedback on in the tech preview period
#675 opened Feb 21, 2024 by eemeli
Provide structure in the registry for distinguishing types of options normative registry resolve-candidate This issue appears to have been answered or resolved, and may be closed soon. specification
#663 opened Feb 18, 2024 by macchiati
We should not require * if the variant keys exhaust all possibilities formatting LDML 47 LDML 47 Release (Stable) registry Seek-Feedback-in-Preview Issue should be something we seek feedback on in the tech preview period syntax Issues related with MF Syntax
#603 opened Jan 15, 2024 by eemeli
Should we really be using {{pattern}} and |literal| delimiters? LDML 47 LDML 47 Release (Stable) question Further information is requested Seek-Feedback-in-Preview Issue should be something we seek feedback on in the tech preview period syntax Issues related with MF Syntax
#602 opened Jan 15, 2024 by eemeli
ProTip! Type g i on any issue or pull request to go back to the issue listing page.