Localization

[wanderingstan]

We can't be English/America-only. Let's get this DApp global!

Overall plan is:

Step 1: Choose localization library. Default choice for React would seem to be: react-localization

Step 2: Break apart current english strings and replace with appropriate l10n calls.

Step 3: Get translations for different languages.

If you have an opinion on 1, or want to do some research, that'd be very useful. Step 2 will be the bulk of this issue.

Sub-tasks created:

• Whitepaper and product brief links in footer should be language-aware #245
• Add language selection dropdown menu #246
• Replace sentence concatenation with full sentences that can be translated #247
• Localize <Timelapse> component #248
• Complete wrapping of strings with <FormattedMessage> component #249
• Research and implement a way to localize react-jsonschema-form #255
• Localization - Integrate with Crowdin #263

[micahalcorn]

@wanderingstan do you want to link us here to the implementation(s) that you saw for us to reference?

[gaboesquivel]

this is a nice another lib for internationalization https://github.com/i18next/react-i18next

[wanderingstan]

John J and I had discord convo on this, with me forgetting g we already had an open issue.

His comment there:

cool - I'll look at swarm's stuff but I think this is the winner in terms of react i18n stuff:
https://www.npmjs.com/package/react-intl

[jordajm]

react-i18next looks cool too though - worth checking out for sure - and @wanderingstan found this for translating between the json files it uses and .po/.pot files of gettext
https://www.npmjs.com/package/react-intl-po

[wanderingstan]

For reference: Here is our translation files & workflow or the website:
https://github.com/OriginProtocol/company-website/tree/master/translations

[jordajm]

WIP PR:
#238

[micahalcorn]

Considered done with #263 split into sub-tasks ✅