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.

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

Recovery from data model errors #735

Open
catamorphism opened this issue Mar 19, 2024 · 1 comment
Open

Recovery from data model errors #735

catamorphism opened this issue Mar 19, 2024 · 1 comment
Labels
errors Issues related to the errors section of the spec LDML46 Items that must be first for post-tech preview (LDML46) specification

Comments

@catamorphism
Copy link
Collaborator

I think we haven't decided yet whether data model errors should be recoverable. The current version of formatting.md says they are not recoverable:

If the message being formatted has any Syntax Errors or Data Model Errors, the result of pattern selection MUST be a pattern resolving to a single fallback value using the message's fallback string defined in the formatting context or if this is not available or empty, the U+FFFD REPLACEMENT CHARACTER �.

However, #703 would delete "data model errors" from that text.

So, do we want to require the behavior as currently specified; or leave it up to the implementation whether to replace a smaller piece of the message with a fallback, or replace the entire message with a fallback?

@catamorphism catamorphism added specification errors Issues related to the errors section of the spec LDML46 Items that must be first for post-tech preview (LDML46) labels Mar 19, 2024
@macchiati
Copy link
Member

This feels like a post-45 issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
errors Issues related to the errors section of the spec LDML46 Items that must be first for post-tech preview (LDML46) specification
Projects
None yet
Development

No branches or pull requests

2 participants