WIP: Idea for handling of translations: Using same JSON structure for translation files #510
+96
−0
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
Closed
|
Keys for arrays could be determined from We need to mark fields which are language-dependent. Open question: Is this information also part of JSON-schema |
|
We want to take the approach of .properties files. Therefore, I close this draft |
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.
See #106.
This PR shall show one possible approach how translations could be stored in separate JSON files (one file per language and JSON file).
The filename pattern would be
<object name>.<object type>.<language>.json.The content of the JSON file shows following fields of the original ABAP file format (JSON representation):
formatVersion