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

Add support for Project Fluent #853

Open
michalfita opened this issue Aug 16, 2024 · 2 comments
Open

Add support for Project Fluent #853

michalfita opened this issue Aug 16, 2024 · 2 comments

Comments

@michalfita
Copy link

Project Fluent is new approach to software translations that doesn't promote English first approach to translated texts. It's much more advanced than simple .po files, but it's gaining traction in Rust projects and web projects.

It would be nice if most popular translation editor on the planet can handle this new format.

@vslavik
Copy link
Owner

vslavik commented Aug 16, 2024

Project Fluent is new approach

Aka everything old is new again... While the syntax is nicer, the approach is not fundamentally different from ICU MessageFormat.

As must be clear to you from even cursory reading of the spec (or, rather, a tutorial), adapting the UI to this would be major undertaking, with many small and not-so-small steps — that's a big ask for what is still relatively obscure format. But it would be nice to have, yes, and a lot of that would be shared with ICU or JSON support. You're most welcome to start contributing towards the goal, and your PRs will be most appreciated.

Poedit now has better support for symbolic IDs - that's a good first step. Clarifying the Fluent spec 1 or where do the strings come from 2 would be another. Providing docs on tooling used (updating, extraction, naming files etc.)

Footnotes

  1. E.g. where do the variables come from, how can Poedit validate them, how can the translator know what they can or should use etc.

  2. Because for all the talk about "not promoting English-first approach", translators do need reference text and symbolic IDs are crap for that.

@michalfita
Copy link
Author

While the syntax is nicer, the approach is not fundamentally different from ICU MessageFormat.

Point taken. Mozilla was inspired by that. Then I haven't seen any software actively using ICU approach which seem to have really borked interface to C++.

You're most welcome to start contributing towards the goal, and your PRs will be most appreciated.

I'm not saying "no", but my relationship with wxWindows is rather unfriendly. I could try to work on some loading attempts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants