Solved

Spell Checker fails on punctuation

when I turn on spell checking it gives me an error for all punctuation marks In the attached you can see the the spell checker- considers a stand alone ? as a spelling mistake, which can be easily resolved by adding ? to the dictionary but it is a real pain- considers Done? as Done being spelled incorrectly, which cannot be easily resolved as you have to have every word with every punction mark in the dictionary. p.s. I find it strange that I can't attach .bmp files to posts.

Best Answer
photo

Dear Users,

We gladly announce that this problem has been solved in the recent December 2012 release (version 2.4.0.8).

Best regards,

photo
0

This happens to me too, for the spell checker in Portuguese...

photo
0

(

)

-

The english spell checker correctly ignores the following, treating them as non existent (this:com is an error but this: com is not). The behavior for these should be the same as the other punctuation above.

;

:

The english spell checker correctly requires a ' to be used only in a proper contraction.

The english spell checker correctly ignores the following, treating them as spaces (this.com is not an error)

"

,

.

The english spell checker correctly ignores numbers, unless the number is accompanied by punctuation. The user should have the option to automatically ignore any string that contains a number.

The english spell checker has an error when it treats any string containing or adjacent to the following as misspelled. Behavior should be the same as the other punctuation above that are treated as a space character:

<return>

<line feed>

!

[

]

{

}

=

+

_

|

@

#

$

%

^

*

`

~

<

>

Many spell check tools can be configured to treat any character in a particular set as a space character, to ignore any string that contains characters in a second set as non words, and to toggle the ability to ignore any string that contains a number.

The ability to configure these behaviors should be added to a future version spell checker to increase the utility of this feature.

photo
0

Dear Users,

Thank you for your feedback.

We will look into this issue and keep you posted.

Best regards,

photo
0

Dear Users,

We gladly announce that this problem has been solved in the recent December 2012 release (version 2.4.0.8).

Best regards,