"Can not" should be "cannot". "Can not" has a different meaning than "cannot".

CommentFileSizeAuthor
#3 change_can_not_to_cannot-2277879-3.patch3.63 KBaohrvetpv
#1 change_can_not_to_cannot-2277879-1.patch1.06 KBaohrvetpv

Comments

aohrvetpv’s picture

aohrvetpv commented
Status: Active » Needs review
StatusFileSize
new change_can_not_to_cannot-2277879-1.patch1.06 KB
aohrvetpv’s picture

aohrvetpv commented

Needs to be fixed in other constraints too. Patch forthcoming.

aohrvetpv’s picture

aohrvetpv commented
Title: Grammatical error in history constraint description and message » "Can not" should be "cannot" in various places
StatusFileSize
new change_can_not_to_cannot-2277879-3.patch3.63 KB
aohrvetpv’s picture

aohrvetpv commented

Example:
"Password can not have more than this number of identical consecutive characters."

can be read as

"Password is able to not have more than this number of identical consecutive characters."

which is the opposite of the intent.

Some people seem to argue that "can not" is equally valid, but even if considered valid, "cannot" is less prone to misinterpretations such as the above.

deekayen’s picture

deekayen commented
Version: 7.x-2.x-dev » 7.x-1.x-dev
Status: Needs review » Patch (to be ported)

  • Commit 711fd9e on 7.x-2.x authored by AohRveTPV, committed by deekayen: 
    Issue #2277879 by AohRveTPV: Fixed "Can not" should be "cannot" in...
aohrvetpv’s picture

aohrvetpv commented
Status: Patch (to be ported) » Fixed

Verified "can not" exists neither in 7.x-1.x nor 6.x-1.x.

Originally I thought "can not" was flatly wrong, but as I posted before, it is not agreed upon. "cannot" has no chance of misinterpretation, so it seems to make sense to prefer it.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.