-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WPF on .NET 8.0 > TextBox.SpellCheck custom dictionary has no effect #9760
Comments
Do you have a repro project? |
@miloush I created a public repo with a minmal reproducible sample, you can find it here: https://github.com/LukinTV/WPF-SpellCheck-CustomDictionary. Just be sure to change the absolute path to the .lex-file to wherever you cloned to project: txtSpellCheck.SpellCheck.CustomDictionaries.Add(new Uri(@"C:\temp\Repro\WPF-SpellCheck-CustomDictionary\custom.lex", UriKind.Absolute)); |
Reference #9701 |
Also, https://stackoverflow.com/questions/77258504/wpf-spellcheck-on-windows-11-systems/. |
I've tried to investigate the problem, but I've had no luck |
Even with default spell check it sometimes works and sometimes not |
This issue has been moved from a ticket on Developer Community.
[severity:I'm unable to use this version]
Hello,
I am currently facing the problem that the SpellCheck of the TextBox WPF-Control does not seem to load my lexicon file correctly.
Per documentation I am using the following code to load the dictionary:
The TextBox is defined in XAML as follows:
The file "test.lex" contains the following lines:
Still, when I type the word "Datenbox" in the TextBox control, it underlines the word and tries to correct it.
When I retrieve the custom dictionaries using "SpellCheck.GetCustomDictionaries", I can see that the dictionary was in fact loaded. It just isn't applied for some reason.
Project Information:
Any help or hints would be greatly appreciated!
Kind regards,
Lukas
Original Comments
Feedback Bot on 9/11/2024, 07:10 AM:
(private comment, text removed)
Original Solutions
(no solutions)
The text was updated successfully, but these errors were encountered: