Skip to content
This repository has been archived by the owner on Apr 15, 2019. It is now read-only.

Choose and set up a localization platform #736

Closed
slaweet opened this issue Sep 12, 2017 · 1 comment
Closed

Choose and set up a localization platform #736

slaweet opened this issue Sep 12, 2017 · 1 comment
Assignees
@slaweet
Labels
chore *medium

Comments

@slaweet
Copy link
Contributor

slaweet commented Sep 12, 2017

After i18n is set up in #3 we should set up a localization platform to separate translation management from development.

With a localization platform, we can store the translations separately from the source code and download the latest translations automatically as one step of npm run build.

There should also be a command for downloading the latest translations when necessary.

Uploading latest transaction sources can be part of building development branch in Jenkins.

I have personally good experience with https://www.transifex.com
But there are other options, like https://crowdin.com
@slaweet slaweet added the chore label Sep 12, 2017
@slaweet slaweet self-assigned this Sep 20, 2017
@slaweet slaweet mentioned this issue Sep 25, 2017
Merged
@slaweet
Copy link
Contributor Author

slaweet commented Oct 20, 2017

Done. We use https://translate.lingohub.com/liskhq/lisk-nano/dashboard

@slaweet slaweet closed this as completed Oct 20, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@slaweet slaweet

Labels
chore *medium
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@slaweet