You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my opinion, those folks who make an effort for their code quality, documentation and spelling will use tools like codespell. Those folks who can't be bothered and want things to be informal, would mostly likely not be using quality checking tools.
The results from hunspell, aspell and ispell. All of them indicate a misspell and proposed JavaScript.
When I am typing this reply using Chrome browser, the browser recognises Javascript as misspelled, the word is underlined with a wavy red line. When I type in CamelCase, the wavy red line disappeared.
I understand codespell is not supporting CamelCase now, but it should not prevent us from getting dictionary in shape. IMO, the dictionary should hold true to what it should be. Not based on informal folks way of writing. People will then feel confident. @peternewman what do you think?
I understand codespell is not supporting CamelCase now
It wouldn't find JavaScipt as a scipt->script typo, but the replacements can be any case and the magic guesser will try and match them during replacemenet based on the source case.
but it should not prevent us from getting dictionary in shape. IMO, the dictionary should hold true to what it should be. Not based on informal folks way of writing. People will then feel confident. @peternewman what do you think?
Agreed, and I've done the same thing in the past with countries etc for the RHS of dictionary entries.
Originally posted by @vikivivi in #2266 (comment)
In my opinion, those folks who make an effort for their code quality, documentation and spelling will use tools like codespell. Those folks who can't be bothered and want things to be informal, would mostly likely not be using quality checking tools.
The results from hunspell, aspell and ispell. All of them indicate a misspell and proposed
JavaScript
.When I am typing this reply using Chrome browser, the browser recognises
Javascript
as misspelled, the word is underlined with a wavy red line. When I type in CamelCase, the wavy red line disappeared.I understand codespell is not supporting CamelCase now, but it should not prevent us from getting dictionary in shape. IMO, the dictionary should hold true to what it should be. Not based on informal folks way of writing. People will then feel confident. @peternewman what do you think?
The text was updated successfully, but these errors were encountered: