Skip to content
This repository has been archived by the owner on Sep 23, 2020. It is now read-only.

[FEATURE]Translations logic #28

Open
gomesalexandre opened this issue Jun 19, 2019 · 1 comment
Open

[FEATURE]Translations logic #28

gomesalexandre opened this issue Jun 19, 2019 · 1 comment

Comments

@gomesalexandre
Copy link

Hi !
I suggest adding logic for translations so it's easy to get the docs translated by the community.

We could inspire from how react does it, which has been working wonders.

If the goal is to make Libra accessible to everyone, translating the dev docs should then be a high priority.

@gomesalexandre
Copy link
Author

gomesalexandre commented Jun 21, 2019

Translations are living in website/i18n/en.json for English, however, it seems like this isn't as simple as creating a translation file (say fr-FR.json) but we'd rather wait for a Crowdin translation project to be created, as managing translations without it will be quite a pain. @endiliey could you confirm ?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant