search

katjam / local-elm

Translation support for programming in Elm
0 stars 0 forks source link

User experience: How to select translations #5

Open marc136 opened 9 months ago

marc136 commented 9 months ago

How should a user select her translation?

So here are three example ideas (continued from https://github.com/katjam/local-elm/issues/1#issuecomment-1826350714)

  1. One executable per locale The user could download a specific build that is translated into one language.
    If it is a forked Elm compiler, she could place it in an executable path and name it elm.

  2. One executable that donwloads translation resource 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.
    The user could use a command like elm-local switch-locale=de or specify an environment variable like $ELM_LOCALE.

  3. One executable with multiple translations built-in The selection of the locale could be the same as with 2, but no downloads would be needed.

Edit: I changed the text, because it does not have to be a compiler fork, it could be any tool.

marc136 commented 9 months ago

I don't know if this post is still the current state inside the rust localization project, but it seems like they are not sure yet how they want to add the translations (2022-08 diagnostics in different languages post).

But for me it is also important that the user actively chooses to get translated error messages.