Hi folks, I have created a tool to build localized versions of your elm apps and to help with the exchange of localized content with translators and product managers.
https://github.com/iosphere/elm-i18n The idea is to avoid including the language in the app's model and to not pass it to each view function that requires localized content. Instead each language is copied (symlinked) into place before running elm-make which allows you to treat localized strings as constants (or functions if you use placeholders). The tool also provides a CLI to export localized strings from Elm to CSV and provides a tool to generate Elm code from CSV (once you receive updates from your translators). I would appreciate your feedback. The readme includes a list of advantages and disadvantages feel free to add your ideas. Kind regards, Felix P.S.: We use this internally for a single-language app to allow non-technical team members to edit all strings of our app. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
