Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Define resolved value formally #678

Open
aphillips opened this issue Feb 22, 2024 · 1 comment · May be fixed by #728
Open

Define resolved value formally #678

aphillips opened this issue Feb 22, 2024 · 1 comment · May be fixed by #728
Labels
formatting LDML46 Items that must be first for post-tech preview (LDML46) normative Seek-Feedback-in-Preview Issue should be something we seek feedback on in the tech preview period

Comments

@aphillips
Copy link
Member

There have been multiple comments on the need to define the term "resolved value", which we use formally but have defined somewhat informally.
@catamorphism
Copy link
Collaborator

Note that this is the goal of #645

@aphillips aphillips added LDML46 Items that must be first for post-tech preview (LDML46) and removed Agenda+ labels Feb 28, 2024
@gibson042 gibson042 mentioned this issue Mar 1, 2024
Merged
@aphillips aphillips added the Seek-Feedback-in-Preview Issue should be something we seek feedback on in the tech preview period label Mar 1, 2024
@eemeli eemeli linked a pull request Mar 14, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
formatting LDML46 Items that must be first for post-tech preview (LDML46) normative Seek-Feedback-in-Preview Issue should be something we seek feedback on in the tech preview period
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add Resolved Values section to formatting unicode-org/message-format-wg
2 participants
@aphillips @catamorphism