Support any developer style language - #1
Open
truong-hua wants to merge 1 commit into
Open
Conversation
Instead of supporting only en_devel, we are now allow user to create any other *_devel
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.
Instead of supporting only en_devel, we are now allow user to create any other *_devel
Proposed changes
The developer style source language happens in any source language but not only english. So we should allow other style, such as id_devel or vi_devel, so that the machine translation can work properly.
Without this change, the Microsoft Terminology API does not work with *_devel (excepts en_devel) because of wrong language code.
Other information
This change is very small