-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Label
Projects
Milestones
Assignee
Sort
Issues list
Create a PR for function interaction
Action-Item
design
Design principles, decisions
formatting
#797
opened May 20, 2024 by
aphillips
Create a design document for error handling
Action-Item
design
Design principles, decisions
errors
Issues related to the errors section of the spec
#796
opened May 20, 2024 by
aphillips
[FEEDBACK] Unpaired bidi isolates should not be a parse error
Preview-Feedback
Feedback gathered during the technical preview
syntax
Issues related with MF Syntax
#788
opened May 13, 2024 by
eemeli
[FEEDBACK] Isolating quoted patterns on the outside adds a lookahead to the syntax
Preview-Feedback
Feedback gathered during the technical preview
syntax
Issues related with MF Syntax
#787
opened May 13, 2024 by
eemeli
[FEEDBACK] Possible simplification of the data model
data model
Issues related with MF data Model
Preview-Feedback
Feedback gathered during the technical preview
#786
opened May 11, 2024 by
tomasr8
Clarify error handling and fix normative requirements
errors
Issues related to the errors section of the spec
LDML46
Items that must be first for post-tech preview (LDML46)
#785
opened May 8, 2024 by
aphillips
Spec language on eager vs. lazy evaluation should be clarified
editorial
LDML46
Items that must be first for post-tech preview (LDML46)
#784
opened May 6, 2024 by
catamorphism
The spec should not force implementations to go against their standard error handling patterns
Action-Item
errors
Issues related to the errors section of the spec
LDML46
Items that must be first for post-tech preview (LDML46)
#782
opened May 6, 2024 by
mihnita
registry.md
needs definitions
editorial
LDML46
#766
opened Apr 11, 2024 by
aphillips
[FEEDBACK] Consider disallowing duplicate attribute names
data model
Issues related with MF data Model
LDML46
Items that must be first for post-tech preview (LDML46)
normative
Preview-Feedback
Feedback gathered during the technical preview
syntax
Issues related with MF Syntax
#756
opened Mar 29, 2024 by
catamorphism
Improve test coverage for built-in function options
LDML46
Items that must be first for post-tech preview (LDML46)
test-suite
#752
opened Mar 25, 2024 by
catamorphism
Create design doc for Design principles, decisions
formatting
LDML46
Items that must be first for post-tech preview (LDML46)
.match
declaration/non-declaration
Action-Item
design
#747
opened Mar 25, 2024 by
aphillips
Create design doc for bidi support inside messages
Action-Item
design
Design principles, decisions
LDML46
Items that must be first for post-tech preview (LDML46)
syntax
Issues related with MF Syntax
#746
opened Mar 25, 2024 by
aphillips
What is the behavior of Items that must be first for post-tech preview (LDML46)
registry
:number
when passed an option with a non-integer value?
LDML46
#739
opened Mar 19, 2024 by
catamorphism
Is it an error to pass a bad option to a function?
errors
Issues related to the errors section of the spec
LDML46
Items that must be first for post-tech preview (LDML46)
#738
opened Mar 19, 2024 by
catamorphism
Recovery from data model errors
errors
Issues related to the errors section of the spec
LDML46
Items that must be first for post-tech preview (LDML46)
specification
#735
opened Mar 19, 2024 by
catamorphism
syntax.md and message.abnf can get out of sync
LDML46
Items that must be first for post-tech preview (LDML46)
specification
#734
opened Mar 18, 2024 by
catamorphism
Consider adding a token grammar
LDML46
Items that must be first for post-tech preview (LDML46)
specification
#729
opened Mar 14, 2024 by
catamorphism
[FEEDBACK] Message Format Unquoted Literals
Preview-Feedback
Feedback gathered during the technical preview
syntax
Issues related with MF Syntax
#724
opened Mar 13, 2024 by
macchiati
[FEEDBACK] syntax: two ambiguities in the reserved-statement rule
Preview-Feedback
Feedback gathered during the technical preview
syntax
Issues related with MF Syntax
#721
opened Mar 11, 2024 by
bhaible
[FEEDBACK] incorrect comment in message.abnf
Preview-Feedback
Feedback gathered during the technical preview
syntax
Issues related with MF Syntax
#720
opened Mar 11, 2024 by
bhaible
[FEEDBACK] The data model could be simplified for declarations
data model
Issues related with MF data Model
Preview-Feedback
Feedback gathered during the technical preview
#718
opened Mar 9, 2024 by
eemeli
[FEEDBACK] The data model could be simplified for literals
data model
Issues related with MF data Model
Preview-Feedback
Feedback gathered during the technical preview
#717
opened Mar 9, 2024 by
eemeli
[FEEDBACK] The data model could be simplified for options and attributes
data model
Issues related with MF data Model
Preview-Feedback
Feedback gathered during the technical preview
#716
opened Mar 9, 2024 by
eemeli
Simpler description of the matching algorithm
formatting
Preview-Feedback
Feedback gathered during the technical preview
#715
opened Mar 9, 2024 by
macchiati
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.