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

Using or switching to icu4x crates? #329

Open
waywardmonkeys opened this issue Sep 7, 2023 · 4 comments · May be fixed by #335
Open

Using or switching to icu4x crates? #329

waywardmonkeys opened this issue Sep 7, 2023 · 4 comments · May be fixed by #335
Assignees
Labels
icu4x Migrate example components to use icu4x instead of custom stubbed out components.

Comments

@waywardmonkeys
Copy link
Collaborator

Since icu4x is now in existence and much further along now than it was when fluent-rs was actively being developed, is it worth looking at switching some functionality to using those crates?

I think there may be some logistical difficulties at first, but is there interest? Would it be useful? Would it help with providing some of the formatters or better handling of plural rules or ... ?

@zbraniecki
Copy link
Collaborator

@eemeli I plan to take on this if you're comfortable with me switching us over.

@zbraniecki zbraniecki linked a pull request Dec 14, 2023 that will close this issue
@eemeli
Copy link
Member

eemeli commented Dec 14, 2023

@zbraniecki Sure, go for it!

@waywardmonkeys
Copy link
Collaborator Author

Happy to see this! I'd been putting off doing anything on it pending projectfluent/fluent#358 as I wasn't sure that anything I did would actually get merged and it has been 3 months with no visible progress on that...

@alerque alerque added the icu4x Migrate example components to use icu4x instead of custom stubbed out components. label May 6, 2024
@alerque
Copy link
Collaborator

alerque commented May 6, 2024

I'm going to be gradually trying to work through issue triage. I'm doing some things like assigning issues that are already in progress or people have said they are working on to them, but please understand that isn't to put pressure on it to move along, just to avoid duplicate work. If other people want to contribute to the same issues I would just encourage them to open PRs against the branch(es) where that work is already in progress and collaborate on it. Also if I assign anything to anybody you don't want to be listed on just recuse yourself, no worries at all ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
icu4x Migrate example components to use icu4x instead of custom stubbed out components.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants