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

Investigate some potentially related projects #1

Open
1 task
katjam opened this issue Aug 30, 2023 · 1 comment
Open
1 task

Investigate some potentially related projects #1

katjam opened this issue Aug 30, 2023 · 1 comment

Comments

@katjam
Copy link
Owner

katjam commented Aug 30, 2023

@marc136
Copy link
Collaborator

marc136 commented Nov 25, 2023

If we want to use project-fluent translations in the compiler, I did not find a nice library to use .ftl translations files directly in Haskell.
But we could follow a similar approach as elm-fluent to generate Haskell code from the translation files.

Or maybe someone smart can come up with a library, that maybe works similar to this gettext example where the translations are loaded at runtime from translation files.
This would be strange at first, because one compelling thing about Elm is that it is a single binary. But maybe it won't be so bad, if the additional translation files are only download when requested by the user and stored in $ELM_HOME.

Or all translations could be baked into the compiler, and we need a mechanism to allow switching the output locale (e.g. ENV var or a command line argument).

Before I derail this thread too much, I'll add more about this in #2.

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

No branches or pull requests

2 participants