Codespell report for "GIMP" (on fossies.org)
The FOSS server fossies.org - supporting "GIMP" for many years - offers among others a feature "Source code misspelling reports". Such reports are normally only generated on request, but as Fossies administrator I have just created for testing purposes such a codespell based analysis for the new GIMP release 2.10.20:
https://fossies.org/linux/misc/gimp/codespell.html
That version-independent (not linked) URL should redirect always to the last report (if available).
After a first review the file ChangeLog was excluded since it contains 630 (!) errors (roughly 80% percent of all found errors). Although after further reviews some obviously wrong matches ("False Positives" = FPs) are already filtered out (ignored) please inform me if you find more of them so that I can force a new improved check if applicable.
Just for information there are also two supplemental pages showing some used "codespell" configuration details and all obvious False Positives.
Ok, most of the errors are "only" in comments and are therefore not directly visible or relevant for users, but some are found in output strings and three errors affect the source code itself (that case is marked in the report often by a "?" since the displayed context type wasn't determined):
"bounrady -> boundary" at line 62 in file app/core/gimpboundary.c
"simily -> smiley" at line 11 in file plug-ins/gfig/gfig-examples/Makefile.am
"evnet -> event" at line 1049 in file tools/performance-log-viewer.py
A similar but continuously updated report is available for the GIMP GitLab "master" version but using a special restricted "test" folder that isn't really integrated into the standard Fossies services and should also not be accessible to search engines:
https://fossies.org/linux/test/gimp-master.tar.gz/codespell.html
That version independent URL hopefully always redirects to the report for the latest "master" version identified by the short commit ID and a year-month-day string (YYMMDD) representing the according git pull date (mostly = commit date). The refresh rate is currently half-hourly.
A little bit surprisingly most of the found spelling errors are already fixed in that development code. Especially also the last two of the above mentioned errors in the code itself (already six months resp. one year ago).