# Looking for feedback on a new I18n Solution for Elm

**URL:** <https://discourse.elm-lang.org/t/looking-for-feedback-on-a-new-i18n-solution-for-elm/7969>\
**Category:** Request Feedback\
**Created:** [December 5, 2021, 5:00pm UTC](https://discourse.elm-lang.org/t/looking-for-feedback-on-a-new-i18n-solution-for-elm/7969 "2021-12-05T17:00:00Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![andreasmolitor](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/andreasmolitor/32/4384_2.png) [@andreasmolitor](https://discourse.elm-lang.org/u/andreasmolitor)\
**Post date:** [December 5, 2021, 5:00pm UTC](https://discourse.elm-lang.org/t/looking-for-feedback-on-a-new-i18n-solution-for-elm/7969/1 "2021-12-05T17:00:00Z")

</div>

Hi Elm community, long time lurker here 🙂

I recently stumbled over [A vision for data interchange in Elm](https://gist.github.com/evancz/1c5f2cf34939336ecb79b97bb89d9da6) and Protobuf and was inspired by the approach to use compile time to optimize client-server communication. I noticed I was loading reasonably large JSON files containing static texts for internationalization and wondered if I could optimize that. What I’m doing now is converting common I18n Formats (.json and .properties so far) to a flat JSON array as well as replacing placeholders by simple numbers.

There are a couple of existing I18n generators for Elm but as far as I could tell, they did not go as far as my approach in terms of optimization (more on the differences in the README).

I would love if you could give me some feedback/give my package a try.

> **[GitHub - andreasewering/elm-i18n: Compile time internationalization for Elm...](https://github.com/andreasewering/elm-i18n)**
>
> Compile time internationalization for Elm supporting multiple input and output formats - GitHub - andreasewering/elm-i18n: Compile time internationalization for Elm supporting multiple input and ou...

I want this to be a useful addition to the community, so if you have any feature requests go ahead and I will probably implement them 🙂

Currently I’m writing a webpack plugin wrapping this package as well.

---

<div class="post-metadata">

**Author:** ![francescortiz](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/francescortiz/32/1721_2.png) [@francescortiz](https://discourse.elm-lang.org/u/francescortiz)\
**Post date:** [December 7, 2021, 7:55am UTC](https://discourse.elm-lang.org/t/looking-for-feedback-on-a-new-i18n-solution-for-elm/7969/2 "2021-12-07T07:55:00Z")

</div>

Hi, the README is missing the supported formats, and I think that it is key in order to consider adoption. Could you update it? Thanks!

---

<div class="post-metadata">

**Author:** ![andreasmolitor](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/andreasmolitor/32/4384_2.png) [@andreasmolitor](https://discourse.elm-lang.org/u/andreasmolitor)\
**Post date:** [December 7, 2021, 1:06pm UTC](https://discourse.elm-lang.org/t/looking-for-feedback-on-a-new-i18n-solution-for-elm/7969/3 "2021-12-07T13:06:19Z")

</div>

The supported formats are in the “Feature Overview” at the moment, but I should probably make an extra section for that. Especially because I got a request to support Fluent syntax as well.

Thank you for your feedback.

---

<div class="post-metadata">

**Author:** ![Laurent](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/laurent/32/2051_2.png) [@Laurent](https://discourse.elm-lang.org/u/Laurent)\
**Post date:** [December 9, 2021, 6:57am UTC](https://discourse.elm-lang.org/t/looking-for-feedback-on-a-new-i18n-solution-for-elm/7969/4 "2021-12-09T06:57:54Z")

</div>

I noticed the current npm version is 2.1.4, but there are no releases on GitHub. You can create GitHub releases easily if you bump your version with [npm version](https://docs.npmjs.com/cli/v8/commands/npm-version) and then do a `git push && git push --tags` before `npm publish`.  
I have a custom compile-time i18n process (language directories with plain elm files full of string constants) but I’m following your GitHub releases now 😉

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex035/uploads/elm_lang/original/1X/50a05e53677a2c3b47776d7abd0f113eb50193a1.png) [@system](https://discourse.elm-lang.org/u/system)\
**Post date:** [December 19, 2021, 6:58am UTC](https://discourse.elm-lang.org/t/looking-for-feedback-on-a-new-i18n-solution-for-elm/7969/5 "2021-12-19T06:58:26Z")

</div>

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.