Bug 63923 - Some more spelling errors
Summary: Some more spelling errors
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: All (show other bugs)
Version: 2.5-HEAD
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Depends on:
Reported: 2019-11-13 20:50 UTC by Jens Schleusener
Modified: 2021-04-18 09:53 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Jens Schleusener 2019-11-13 20:50:25 UTC
On the FOSS server fossies.org I recently added a new feature "Source code misspelling reports". Animated by the bug report https://bz.apache.org/bugzilla/show_bug.cgi?id=62960 I have now done such a check for the current trunk version of "httpd" (since there some spelling errors contained still in the release version are already patched):


That URL hopefully redirects always to the last available report, currently to


Since I am neither a real coder nor a native or good English speaker I have not yet created a patch file since the risk is too high that something would be wrongly corrected. But if that is really required I would do that but only for the very obvious spelling errors and typos.

The analysis, that uses as basis the command line tool "codespell" (https://github.com/codespell-project/codespell) has found still 261 occurrences of 194 different spelling error types (so most of the errors occur only once).

Maybe some are False Positives but to minimize them some matched words were for "httpd" manually excluded (see the according page

Especially also the words "depandancies" (130 matches) and "creater" (48 matches) were finally excluded to make the page clearer, but not in a first run that was done for the last httpd release 2.4.41:


By the way, the reports show the top found spelling error types and a sortable list of all found errors together with the suggested fixes, the affected member files and the according line numbers. Clicking on a red colored spelling error in the "top" list jumps to the first match in the actual spelling error occurrence list. Clicking on a matching member file let you browse that file while jumping to the according red marked line containing the error (in some cases the matching line may lie in the neighborhood).

And a further remark: Most errors are found "only" in the documentation or in the code comments, but at least the following seven are in the code itself (but probably and hopefully they are uncritical):

 "resrouce" -> "resource"

 "consideres" -> "considers" or "considered"

 "errror" -> "error"

 "Adminstrator" -> "Administrator" (multiple occurrences)

 "avaialable" -> "available"

 "concatinated" -> "concatenated"
 "Connnection" -> "Connection"

Maybe that information helps a little bit.

Comment 1 Christophe JAILLET 2019-11-14 17:29:09 UTC

I'll give a look at it, especially on the doc and on the one you have spotted above.
Comment 2 Jens Schleusener 2020-01-18 10:31:49 UTC
I have made a new spelling check for the current trunk version so


is now an alias for


After all, roughly 7% of the errors seem to have been corrected.
Comment 3 Jens Schleusener 2020-01-30 18:02:56 UTC
Again a new spelling check for the current trunk version was done so


is now an alias for


As a small new feature there was added a - also sortable - one letter column ("T") indicating the context type of the found spelling error:

 Abbreviations for the current supported context types:
  t = text file line
  c = commented line
  C = Comment block
  F = Formatted text file line
  D = Debug string
  E = Error string
  P = Print string
  Q = Quoted string
  ? = Unassigned context (maybe source code)

That may make it in some cases easier (especially after sorting) to found the more interesting errors.

By the way, the line numbers of the especially mentioned errors 4 and 7 have changed slightly:

 "Adminstrator" -> "Administrator" (also at line 806, 962 and 1052)

 "Connnection" -> "Connection"
Comment 4 Christophe JAILLET 2020-02-15 15:46:06 UTC
r1873985 should have fixed most, if not all, all them.

Could you re-run the analysis?
Comment 5 Jens Schleusener 2020-02-15 16:58:42 UTC
It looks much better!

I have now automated the process (but using the GitHub mirror) so under the given URL


one can always find a fresh analysis (currently with hopefully max. 10 minutes delay after the sources were changed).

And the same now additionally also for 2.4.x

Comment 6 Christophe JAILLET 2020-02-15 21:51:51 UTC
Great, Thx :)
Comment 7 Jens Schleusener 2021-04-18 09:53:09 UTC
Since a new T&R is scheduled next week, I would like to refer again to the page


While some typos have been fixed, of course some have been added and others have been rediscovered through expanded dictionaries. 

By the way, a history page has been added


(caused by later code changes the given line numbers may be not always correct).

If false positives exist (which is likely), please report them so they can be corrected.