Skip to content

ICU4X TC concerns about data-dependent function options #1006

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
Closed
Manishearth opened this issue Feb 13, 2025 · 6 comments
Closed

ICU4X TC concerns about data-dependent function options #1006

Manishearth opened this issue Feb 13, 2025 · 6 comments
Labels
LDML47 LDML 47 Release (Stable) normative Issue affects normative text in the specification Preview-Feedback Feedback gathered during the technical preview

Comments

@Manishearth
Copy link
Member

ICU4X-WG discussed approving the MessageFormat 2.0 spec today (with @eemeli). We had a bunch of questions answered which helped our planning for the implementation

We also had some feedback / requests, specifically around the ability for data-dependent options for functions (u:locale, notation, etc) to depend on external input (or even be expected to change between locales). This does not work well with ICU4X's data loading model.

I plan to write a longer doc explaining the situation, but @eemeli asked me to file an issue for this so it can be tracked by MF2.0. Once I have a doc I shall post it, as a personal contribution, with pending approval from ICU4X-TC as its official position.

Raw discussion here: unicode-org/icu4x#3028 (comment)
@aphillips aphillips added normative Issue affects normative text in the specification Agenda+ Requested for upcoming teleconference Preview-Feedback Feedback gathered during the technical preview LDML47 LDML 47 Release (Stable) labels Feb 13, 2025
@aphillips
Copy link
Member

@macchiati referred to this in the v47 status email, with a proposal to make option=$variable optional behavior.

@Manishearth Thanks for filing this and in advance for documenting the issue.

@Manishearth
Copy link
Member Author

Manishearth commented Feb 14, 2025 •
edited
Loading

We've penned our feedback. It does not count as official TC feedback until @zbraniecki has a look, however it should provide MFWG members an idea of the general shape of the ICU4X team's opinions.

Feel free to request commenter access.

https://docs.google.com/document/d/1ZJ2v8URmNuJh5E5w_CdLwk0hqOkK8pVUe44YFQuc1nY/edit?usp=sharing

@aphillips
Copy link
Member

@sffc Can I make #976 a dupe of this?

@sffc
Copy link
Member

sffc commented Feb 14, 2025

@sffc Can I make #976 a dupe of this?

If this issue is resolved, then yes, #976 is implementable, but it might still involve forcing clients to download more language packs, which is a question I'd like MF WG to resolve separately.

This was referenced Feb 17, 2025
Merged
Merged
@Manishearth
Copy link
Member Author

For the purposes of the meeting today I think it is worth getting answers to two questions:

  • For the options ICU4X listed, does MFWG believe there are genuine use cases for allowing them to be set at run time via external input?
  • If not, does it make sense to disallow them being set in such a way, or will that be confusing to users?

@aphillips aphillips removed the Agenda+ Requested for upcoming teleconference label Feb 17, 2025
@aphillips
Copy link
Member

Hopefully this has been resolved by today (2025-02-17's) call. Reopen if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
LDML47 LDML 47 Release (Stable) normative Issue affects normative text in the specification Preview-Feedback Feedback gathered during the technical preview
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@aphillips @sffc @Manishearth