Underlining spelling errors in strings is very handy and saves QA sending things back for silly typos !
In comments (for us) the text often contains special tech words and abbreviations so ends up with a lot of underling which is quite distracting - probably a lot of users do the same thing
Could you consider splitting this into two options
a) underline spelling errors in strings b) underline spelling errors in comments
An interesting suggestion. I have put in a feature request to see what our developers make of it:
case=30007
If you can collect together these custom words, perhaps by adding them to a custom word list on a single machine, you should be able to turn this word list into a OpenOffice.org format dictionary file which can then be added to VA, see the "Additional Dictionaries" section here:
It is not really a case of "custom" words so much as not really caring about the spelling for comments particularly with all the TLAs and abbreviated text-message style spelling that goes on.
If you could do this then we could just untick checking comments and not be distracted.
One other point to extend the scope of this request - the string checking does not seem to work in resource files for C++ (*.rc) - unless I am missing a setting ?
It would be very useful if it did since this is where most of the public facing text ends up for menus, dialogs and help prompts and most typos are important.
If you press the spell check button on the VA toolbar, or use the menu item:
VAssistX -> Tools -> Spell Check...
then VA spell checking should work correctly for you in a .rc file. Currently VA does not seem to do any underlining in .rc files. The fact that they have their own syntax is going to be a factor.
Spelling errors in comments/strings
Posted - Jul 23 2009 : 08:08:42 AM
