233 auto translation flag #109
Merged
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
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.
The changes described in this PR are related the changes included in cioos-siooc/metadata-entry-form#302
This PR contributes to solving the problem outlined in cioos-siooc/metadata-entry-form#233
The key features and fixes introduced are summarized as follows:
ymlfile extension in the sample command listed in the READMEenv/to the.gitignorerecord.ymlfile to include the auto-translation message for title, abstract, limitations, and platform description.main.j2jinja template, added the variables storing auto-translation method message for title, abstract, limitations, and platform descriptionbilingual.j2jinja template to look for and include the translation method message astranslationKey