Mark up strings for translation and add ES & ID translations#57
Open
stevenday wants to merge 3 commits into
Open
Mark up strings for translation and add ES & ID translations#57stevenday wants to merge 3 commits into
stevenday wants to merge 3 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For an ongoing project at Open Ownership we wanted to make some localised versions of Bluetail for Mexico and Indonesia. The first step towards this was to mark up the text in the UI for translation and add the translations. We've done the latter via Transifex: https://www.transifex.com/open-ownership/bluetail-prototypes/ which I can also transfer if desired?
This is only a very basic approach, you need to manually set a LANGUAGE_CODE to change the language used. This works for us as we're running different installations for each country with different data loaded in, but I didn't want to assume how this might work in other deployments. Hopefully this is useful in this state anyway.