Feature Request: support for I18n

[proddy]

For one on my projects I'm going to have to translate the Web and Console commands to German and possibly other languages. Is there a quick and easy way to isolate all the string literals in React/TS into a separate language file and decide upon building which one to use?

I had a look at react-intl, i18next-react, polyglot and this one called lingui-js but they'll all quite big libraries and there is just not enough progmem to store all the translations to have it real-time.

[rjwats]

react-intl is the way to go I think, 14k min-zipped with tree shaking support. When I remove moment this will be balanced out (moment is big and doesn't tree-shake properly). The tree-shaker would help out here, you could assert a list of support languages in the .env file and have only those ones imported easily enough.

…

On Fri, Jul 17, 2020 at 9:30 AM Proddy ***@***.***> wrote: For one on my projects I'm going to have to translate the Web and Console commands to German and possibly other languages. Is there a quick and easy way to isolate all the string literals in React/TS into a separate language file and decide upon building which one to use? I had a look at react-intl, i18next-react, polyglot and this one called lingui-js <https://medium.com/wantedly-engineering/introduce-multi-language-support-in-a-typescript-react-app-with-lingui-js-f335efcf80d6> but they'll all quite big libraries and there is just not enough progmem to store all the translations to have it real-time. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#175>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKE4VGBJOZFA5WJN4OOH53R4ADZNANCNFSM4O52CCJA> .

[proddy]

thanks. I'll add this to my to-do and report back

[rjwats]

I18n something the framework should be opinionated about really... just not found the time yet.

…

On Wed, Jul 22, 2020 at 10:03 AM Proddy ***@***.***> wrote: thanks. I'll add this to my to-do and report back — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#175 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKE4VBOYBSP3S3TZWJNXG3R42TOJANCNFSM4O52CCJA> .

[proddy]

I went for LinguiJS as it's one of the newer libraries, has a nice CLI and much smaller footprint (react-intl was 13Kb, react-il8next 15Kb and lingujs 4kb zipped).

When hard-coding the languages it works fine. I just wrap esp8266-react's root App component in the library's I18nProvider like:

interface/src/index.tsx

  return (
    <Router history={history}>
       <I18nProvider language="de" catalogs={catalogs_de}>
        <App/>
      </I18nProvider>
    </Router>
  );

now I'd like to make it load the catalogs dynamically when a new language is picked. So replacing the line with

<I18nProvider language={language} catalogs={catalogs}>

Problem now is I haven't found any easy way set a global prop that index.tsx would pick up and use. Any pointers on the best way to achieve this? I was thinking of extending App.tsx but thought I'd ask before I start mangling everything and breaking it all.

[rjwats]

The framework should probably be opinionated about i18n really, so developers can extend their apps with i18n support without needing to roll their own. LinguiJS looks like a reasonable choice - I think bundle size is probably the most important thing in this situation as you have alluded to. Where are you at with this? Still experimenting or is there anything to look at in a PR? I'm thinking it would probably be sensible to extend the features service with a "default" language, and allow users to select a language to be stored and retrieved from local storage.

…

On Tue, Sep 8, 2020 at 8:41 AM Proddy ***@***.***> wrote: I went for LinguiJS <https://lingui.js.org/> as it's one of the newer libraries, has a nice CLI and much smaller footprint (react-intl was 13Kb, react-il8next 15Kb and lingujs 4kb zipped). When hard-coding the languages it works fine. I just wrap esp8266-react's root App component in the library's I18nProvider like: interface/src/index.tsx return ( <Router history={history}> <I18nProvider language="de" catalogs={catalogs_de}> <App/> </I18nProvider> </Router> ); now I'd like to make it load the catalogs dynamically when a new language is picked. So replacing the line with <I18nProvider language={language} catalogs={catalogs}> Problem now is I haven't found any easy way set a global prop that index.tsx would pick up and use. Any pointers on the best way to achieve this? I was thinking of extending App.tsx but thought I'd ask before I start mangling everything and breaking it all. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#175 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKE4VDBP3SYRGCRQRLCYUDSEXN4NANCNFSM4O52CCJA> .

[proddy]

just started, cobbled something together quickly to see how it affected the esp8266's flash mem. It wasn't complex to add as the documentation is good. Extending the feature service sounds like a good idea. My react/TypeScript skills are not as good as yours so I'd probably fudge it. I could create a feature branch in my fork for you to look at, but only changed a few lines

[rjwats]

Internationalization support is very much a worthwhile feature to add. Fortunately the number of strings to internationalize (assuming you ignore the "demo" project) is pretty small too so the bundle shouldn't grow much.

As it happens, one of my work related projects (React) requires internationalization so this will be a useful exercise for me any way. I'm happy to take a look at what you've done so far if you have anything to show - will take a look tonight anyhow and see how it goes.

The goal is clear any way - extensible internationalization with a sensible decision about which library to use.

[rjwats]

LinguiJS is an interesting library. I've not got much to compare it to which is probably the reason I found the workflow to be a little awkward - that's probably par for the course when it comes to i18n though to be fair.

Constructing a const instance of i18n and passing it into the provider seems to give you the most flexibility. I wanted to internationalize the error messages in the JavaScript in the callback code in the SignIn component and this was required in order to do that - as would also be the case for snackbar messages.

Some other notes:

• The TypeScript types in definitely typed sadly aren’t 100% accurate, language is actually optional if i18n is provided and the types don't declare it as such.
• Seems like you have decide whether or not to go with message ids or just "source language" strings. I opted for the latter initially - thinking any attempt to come up with a decent scheme for message ids would end in confusion in the long run.

I think it's worth investigating the other popular libraries before settling. I'm concerned that a single set of message bundles ("catalogues") may be awkward conflict-wise if a downstream project wanted to have it's own internationalized UI sections (your use-case in fact) so that might be worth thinking about when evaluating libraries. Bundle size aside, usability is also obviously very important and I just don't know enough about these liraries yet to make a good judgement.

I have a hacky WIP which demonstrates switching languages with a picker in the app menu bar. I've only internalized the SignIn component though so you have to sign out to see the change.

WIP Commit

[proddy]

wow, that was quick! How you built the LanguageWrapper I would never have figured out myself. I also opted to use po as the language format and followed this guide on how to dynamically compile and load the language files using lingui/loader which I'm hoping saves a little on the Flash mem usage.

(My quick test was in https://github.com/proddy/esp8266-react. I also added the language to sign-in page. I think this is the best place).

[rjwats]

Ah, they provide a HoC to inject the i18n instance into react components. I missed this last night:

https://lingui.js.org/ref/react.html#withi18n

Still, some of our language strings are produced in const scope, that may still require the const instance, take the ntpStatus function here for example:

https://github.com/rjwats/esp8266-react/blob/master/interface/src/ntp/NTPStatus.ts

[rjwats]

My plan is to explore an alternative library tonight to give the evaluation due-diligence.

This looks workable, but need to think about extensiblity for downstream projects still.

[rjwats]

Another quick experiment today, this time with react-intl. Yes, the bundle size is higher, about 25k - so not small at all. I can get this down to a net increase of ~10k though by removing moment which is huge considering what we use from it (really need to do this anyway, moment is insanely large - but we do rely on the UTC offset feature which is not easy to achieve with date-fns IIRC).

On the other hand, this library probably makes for a setup which is easier to document and learn. It certainly seems easier to have multiple message bundles and merge them together (in order keep the "project" messages separate from the "core" messages). I have demonstrated this in the commit below. I haven't implement the switcher, but it's very simliar in the way it works:

Another WIP/Hack

I'm going to continue playing with the js-lingui library to see if I can find a setup which works as well as this one (the separation of message bundles in particular). The smaller minzipped size of that library is a big seller. It seemed it would be more awkward for newcomers to learn being CLI driven (especially on top of the fact they may be new to React and would certainly be new to the framework's idiosyncrasies).

[proddy]

I started looking into this again for one of my projects where 1000+ of the users are German speaking and came across another smaller lightweight i18n implementation by Hofer Ivan. It's very easy to set up, has a small footprint, and is written in lovely TypeScript with a good implementation example for React.

The only place where I struggled was around using its functions inside the render()'s because it uses React's useContext hook to pass the data through the app and we're still using component classes and manually passing props down the tree. Which triggered me into why not port everything over to using hooks #251

[rjwats]

Sounds like a plan. The internationalization frameworks can be chunky so a lightweight alternative would be great. Javascripts Intl package has a lot of what you need for minimal i18n (plural rules, locale date formats) now so I'm not surprised there's a lightweight wrapper (personally I'm ok only supporting modern browsers). I had it in mind that I'd want an approach that would let me keep fragments of these message bundles separated so as to keep the core framework translations separate from the "app" ones to facilitate easier merges. Hopefully this library will facilitate that :) react-intl would... but yeah... chunky library.

…

On Fri, 20 Aug 2021, 09:16 Proddy, ***@***.***> wrote: I started looking into this again for one of my projects where 1000+ of the users are German speaking and came across another smaller lightweight i18n implementation by Hofer Ivan <https://dev.to/ivanhofer/i18n-my-journey-to-a-simple-powerful-and-type-safe-solution-2c46>. It's very easy to set up, has a small footprint, and is written in lovely TypeScript with a good implementation example for React. The only place where I struggled was around using its functions inside the render()'s because it uses React's useContext hook to pass the data through the app and we're still using component classes and manually passing props down the tree. Which triggered me into why not port everything over to using hooks #251 <#251> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#175 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKE4VCPWVFXEJZU36T7M4TT5YFPFANCNFSM4O52CCJA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .