If you want to keep the module's name as is (3 words), then it should be "Equal heights" or "Equal heights jQuery" (no capital "H" in "heights"). Please see here why: #1103208: Projects' names should be checked in .info files for correct capitalization.
"jQuery" is fine as is, because it is a 3rd party project's name (there are similar exceptions for "AJAX" that is an acronym or for "JavaScript").
Alternatively, you could merge the "Equal" & "heights" in one word, like so: "equalHeights" or "equalHeights jQuery", since this is how the author of the 3rd party library we use capitalizes his project's name.
PS: ...it would be better if the module's name was consistent. In its .info it is name = Equal Heights, while the project's name here in d.o it's "Equal Heights jQuery". I'd choose one and stick with it ;)
Comments
Comment #1
klonos...adding proper issue tags ;)
Comment #2
michelleSee #1346158: Decide on coding standard for capitalization of module names [policy, no patch] and #1430452: Use Proper Name Case for core modules for current information on this policy.
Comment #3
klonos...yep, the standard has changed and it now allows (more likely suggests) Proper Name Case instead of the Sentence case for module/theme names. The Sentence case policy remains for UI text like widget labels for example.
Still the name of this project should be as suggested in the issue's title since "equalHeights" and "jQuery" are the respective proper names of 3rd party projects.
Comment #4
drurian commentedComment #6
klonosWell, the standard has been changed for some time now. The name should be "Equal Heights jQuery".
Comment #7
drurian commentedComment #8
klonosThanx Natalia ;)
Comment #8.0
klonos...add note about consistency between module name in .info file and project name in d.o