Spelling - defining text to be checked for spelling
Posted: 2009-11-25 15:36:49
I put this on my wish list for Nisus Pro but it didn't appear so I'm raising it again. It applies most commonly to long documents, one of Nisus's strengths so I think it needs to be addressed.
Let's say I'm on page 23 of a document and I want to check the spelling of that page and that page only. I would like to be able to highlight that page and go to Edit > Spelling > Check Spelling and it would only check the highlighted text. It can't do that yet, though I'm happy to own up to missing something.
I understand the existing parameters of the spelling option. In the case above, if I only want to check the spelling on page 23 then, assuming pages 1 to 22 have been spell checked then it should automatically start at page 23. However, I don't always want to include all words in my dictionary for various reasons so it will always start at the top and proceed until it hits page 23. I know I could always cut and paste page 23 into a new document and do it that way but ...
This is kinda slow and it frustrating. Is that any chance of addressing this issue in a future update?
Thanks and keep up the great work.
Let's say I'm on page 23 of a document and I want to check the spelling of that page and that page only. I would like to be able to highlight that page and go to Edit > Spelling > Check Spelling and it would only check the highlighted text. It can't do that yet, though I'm happy to own up to missing something.
I understand the existing parameters of the spelling option. In the case above, if I only want to check the spelling on page 23 then, assuming pages 1 to 22 have been spell checked then it should automatically start at page 23. However, I don't always want to include all words in my dictionary for various reasons so it will always start at the top and proceed until it hits page 23. I know I could always cut and paste page 23 into a new document and do it that way but ...
This is kinda slow and it frustrating. Is that any chance of addressing this issue in a future update?
Thanks and keep up the great work.