LT-22341: Fix display of spelling errors #621
Closed
Conversation
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
When the user turns off the display of vernacular spelling errors the UseVernSpellingDictionary property is set to false and the SpellCheckingId is set to "<None>" for all of the VernacularWritingSystems. It looks like some projects were backed up when these were not in sync. When we initialize the MorphologyListener we now set the SpellCheckingId’s to "<None>" if the property is false.
|
commit c43f358697: |
Contributor
Author
|
close |
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.
When the user turns off the display of vernacular spelling errors the UseVernSpellingDictionary property is set to false and the SpellCheckingId is set to "" for all of the VernacularWritingSystems. It looks like some projects were backed up when these were not in sync. When we initialize the MorphologyListener we now set the SpellCheckingId’s to "" if the property is false.
This change is