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?
### hunspell: /usr/share/hunspell: en_GB
& Javascript 3 0: JavaScript, Java script, Java-script
### hunspell: /usr/share/hunspell: en_US
& Javascript 3 0: JavaScript, Java script, Java-script
### aspell: /var/lib/aspell: en_GB
& Javascript 4 0: JavaScript, Java script, Java-script, JavaScript's
### aspell: /var/lib/aspell: en_US
& Javascript 4 0: JavaScript, Java script, Java-script, JavaScript's
### ispell: /usr/share/ispell: british-insane
& Javascript 3 0: JavaScript, Java script, Java-script
### ispell: /usr/share/ispell: american-insane
& Javascript 3 0: JavaScript, Java script, Java-script
### look: marcoagpinto/aoo-mozilla-en-dict: en_GB (Marco Pinto)
JavaScript
### look: marcoagpinto/aoo-mozilla-en-dict: en_US (Kevin Atkinson)
JavaScript
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
Javascriptas 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?