localization/translation

[howardchung]

• go through the SPA and move any strings into language files
• figure out routing/persistence of language settings
• figure out how to load/update valve data in multiple languages
• have volunteer translators translate strings

[howardchung]

The current design involves having a JSON file with text strings for each language (en.json, ru.json, etc.). Currently we import lang/en into the components, but I think we'll need to refactor that into a general language component that exports the appropriate language strings based on user selection (perhaps persist language selection to a cookie).

Unfortunately this will not work well for SEO, but having a subdomain for each language won't work well with the SPA.

[dartharaknus]

@howardchung Can you update the status on this issue?

[howardchung]

• Extracting strings: Mostly done but there might be a few random spots with hardcoded strings. I didn't enforce this during the early stages.
• Need to build the LanguageSelector component that presents a selector and saves the chosen option to local storage.
• Ability/item data from Valve is available in multiple languages, but we probably need to move to fetching it from API dynamically import ability, item, hero data #338 to avoid bundling megabytes of data into the JS bundle. For MVP, we could leave that data in English.
• Translation: @albertcui set up https://translate.opendota.com, and we'll mention it in our release post.

[blukai]

I guess we should put the link in footer "Help translate" or smth.

[howardchung]

Sure, we can have a translate link.

[dartharaknus]

Can you make them into separate issues and let's close this.

[howardchung]

Done for 1 and 2. 3 is basically #338 and 4 is done automatically as users submit translations on crowdin. When we add English strings to en.json, it also automatically puts them up for translation.