Adjust Twine format to OrganicsMaps usages #13
+27
−13
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
This aligns with current OrganicMaps structure of: comment = tag = en =
allows: en = en-GB = before alphabetical sorting Aligns with existing and is more logical
OrganicMaps: comment = tags = ref = dev-LANG = other-LANG = Twine original: dev-LANG = ref = tags = comment = other-LANG = fix
|
Do I understand it right that this change is needed to generate Twine/OM strings files from existing android or ios localization files (or other twine-supported formats)? ATM we don't use this conversion at all, only the opposite (from Twine/OM to native platform localizations). Is there some idea to use e.g. Android -> Twine conversion? |
Yes |
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.
This adjust the Twine output format to align with the existing Twine strings.txt in OM
Changes:
Problems: