Projects' names should be checked in .info files for correct capitalization.

I don't know if this would be possible at all (I am sure it would be tricky though)...

If a reviewed project's name is found to 'violate' the capitalization standard, then a check should run against all project's files (like the README & INSTALL files) for occurrences of the wrong string and suggest that it is changed there as well. Possible candidates should be any commends and help text within code that include the project's name.

...project names like 'ImageCache' -that use camel-casing- fall under the same category where not only the first letter of the first word is capitalized. It should be 'Imagecache' or if that name simply seems too ugly, 'Image cache' then. I think that names like 'ImageAPI' should be allowed though, since the 'API' part is an acronym (if not, then perhaps it could be 'Image API' instead).

In cases such as 'CSS Injector' -where the acronym is at the start of its name-, there should be no other capitalization in the rest of the words comprising the project's name. IOW it should be 'CSS injector'.

That's a really nice start Cameron! Thanx.

In order to cover the rest 19% of the cases:

- $project_name should be broken down to a words list/array.
- loop through each word in this list and check it against a list of allowed exceptions (that will need to be kept up to date).
- if the 1st word is not in the exception list, then ucfirst it.
- if the rest of the words are not in the exception list, then strtolower them.
- put/concatenate the separate words back to a single $new_project_name (this can of course be done inside the loop as we go).

...then compare & throw warning.

Now, these are quite a few things to do with a project name and that might already be compliant to our standards in the first place. So, why waste CPU power in such cases? To avoid unnecessary checks, it might be a good idea to do an initial check like so:

- check if only the first letter of the name is upper case and the rest or it lower.
- if not, *only then* run it through our sanitizer process/check.

Well, that leaves us with the rest of the 1% of cases which might be:

- incorrect non-capitalization of words ("cck" instead of "CCK", "jquery" instead of "jQuery" etc.). These will pass the only-first-letter-of-the-first-word rule, but still are not correctly capitalized. We will already have the list of how these are properly capitalized in our sanitizer's exceptions list, so why not check that too?
- things we didn't think of ;)

PS: I kinda like something like $sanitized_project_name or $suggested_project_name better in order to be more descriptive than simply "new".

Yes, I know that there are acceptable exceptions to the standard and these cases were discussed previously in this issue. We seem to agree though that maintaining a complete list of these specific exceptions would not be something possible or -to put it nicely- something worth the trouble. We see no other possible *generic* way to deal with all of them either. We do seem to agree though that *it would be nice* to have a simple check for the generic case where the naming standard seems to be *possibly* broken. In such cases, we could simply through a message that would also link to the standards page. That would probably (and hopefully) be enough to lead to most such cases being "self-healed". Right now, it seems we have no other way to "evangelize" the proper way of naming projects and there seems to be this bad habit/tendency for people to name them however they see fit/nice/cool or however "it's done in other projects" - despite the standard being available and quite clear about it.

Point taken Michelle, but this issue is about using Coder in order to "enforce" a policy that is already in place. Perhaps you need to see this from this perspective and also file a new issue about removing that policy from drupal coding standards. If that issue got accepted and fixed, then I'd be happy to close this one as "won't fix".

I'm sure you understand, since Drupal is someone else's "baby", its coding standards a "baby" of a lot of other people and this issue "my baby" ;)

...the standard has changed. This feature request still stands, but now the "correct capitalization" that we should check for is Proper Name Case for module & theme names. Setting to "postponed" (till we have a 8.x branch for Coder) because it seems that not even core modules will change their case till after D8.

...I will update the issue's summary as soon as Writing .info files (Drupal 7.x) get updated.

Thanx for the heads-up Jennifer. I've updated the issue's summary. Please take a look to make sure I didn't miss anything.

Thanx ;)