-
-
Notifications
You must be signed in to change notification settings - Fork 223
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
Add a "Disable Spellcheck" (or "Keep Proofing Language") Option to Custom Styles #1191
Comments
Just a clarification... OneMore does disable spell checking when you use the Colorize command for inline code. By selecting a run of text within a paragraph and then using the Colorize/lang command, it will apply the primary font chosen in Settings and disable spell check for the affected text (setting the proofing language to Yoruba, with my sincerest apologies to the Yorubians!) Styles are just that and have no association with coding languages. So I think your title is correct, asking for a disable spellcheck option for styles. But considering you get the same functionality by using the Colorize command, do you still need this option on custom styles? |
The way I've been using it is for things like filenames/directory names, class names, menu names, etc. that aren't really code, but are things I need to constantly disable spell check on and set a custom style to (monospace font + font size + font color for filenames / directories and maybe italics + another font color for class names). These might appear several times in a single paragraph, so something that can be hot-keyed per style would be best. I don't really need the Colorize behavior as there's no real coding language to pick, and in several cases I just need a style that disables spell checking (for the case of where I paste a pre-formatted HTML snippet of code and I just want OneNote to not spell check it). So it seemed like just an option on the Custom Styles to disable Spell Check was more appropriate as I'm not really trying to format existing code in these cases. |
Awesome! Thanks for adding it! Look forward to the next release. |
While implemented for the next release, there is a newly discovered OneNote defect, as described by this tech note question. |
I'm not sure if it's at all related to that OneNote bug, but I did notice that selecting a word than has been turned into a hyperlink (to a website URL), and then clicking the OneMore button to "Disable spell checking with selected content" will apply the proofing language to the entire page instead of just the selection. (If the hyperlink is created after disabling spell check, it works fine.) I can create a new issue for that if need be. |
No you're right. This is a OneMore bug, not OneNote. It is due to the fact that OneMore can't tell the difference between a selected text range within a hyperlink and simply placing the text cursor over a hyperlink; even without selecting one or more characters, OneNote indicates that the entire hyperlink is selected. So OneMore has logic to handle this exception, however, the bug you mention above can be fixed and I will do that against this ticket. No need for a new one. |
@Ziflin This will be fixed in the next release. Note however that if only the hyperlink is selected (whether fully, partially, or just because the cursor is on it) then the whole page will be affected. But if even one extra non-hyperlinked character is included then only that range will be affected. |
Problem to Solve
I've been using Onetastic for years solely to have one custom style for "inline code" (
such as this text
) and another for HTML-pasted "code" snippets and both disable spell checking. To get this to work I simply need to have it apply the "Proofing Language" with the styles and have the language set to Latin/etc. similar to how OneMore's custom colorizer does it (#216).New Feature/Solution
Ideally there would be a new option in the Custom Style "Options" section to "Disable Spellchecking" as that is the actual intent. Then OneMore could set the Proofing Language when applying the style similar to how it does with the colorizer.
The text was updated successfully, but these errors were encountered: