NEW Namespace translations, implement into class localisation calls #305
Conversation
This file contains 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
12 tasks
|
@robbieaverill that's what I would do; You'd need to refresh all localisations from transifex, rename the keys (using upgrader), then push up and replace all master keys. To freeze localisations just remove |
|
Ok, thanks. PR at #306 I'll merge it up once merged. |
wilr
force-pushed
the
pulls/2.0/namespace-translations
branch
from
a6950d5
to
1704d1d
Compare
|
Rebased, pushed and waiting for test review. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue #290
@tractorcow do we need to freeze or fork translations for Subsites 3.x compatibility?