Do not capitalize first letters in Arrange fields project's name. [#1423798]

I should be "Arrange fields" instead (no capital "f" in "fields"). Please see this for more info: #1103208: Projects' names should be checked in .info files for correct capitalization.

PS: ...also remember the project's name here in d.o ;)

Comments

Comment #1

richardp CreditAttribution: richardp commented 1 February 2012 at 14:53

Of course I'll do what I can to stay within the Drupal standards, but this one seems weird to me. Maybe it's just American English, I don't know, but since AF is a proper noun, it seems like it both letters should be capitalized.

Ex:

If there was a toy called "Spring Ball", you might write something like:
"I love the Spring Ball I got for Christmas."
You wouldn't say "I love the Spring ball I got for Christmas."

Similar with Arrange Fields. The "Fields" is part of its proper name. To me, this sentence just look weird:
"You should download Arrange fields before breakfast."
This sentence is clearer as to what the module's name is:
"You should download Arrange Fields before breakfast."

The same seems true for other modules, like Vertical Tabs, jQuery Update, Backup and Migrate, etc. Again, this sentence is confusing: "After you download Backup and migrate to your site, you should see...". It looks like the name of the module is just "Backup." The sentence is confusing to me, but a little capitalization makes it much clearer.

Like I said, I will make the modifications to keep within the standards, but has this point ever been raised? And if so, what is the thinking as to why the other method was selected?

Thanks
Richard

Comment #2

klonos

he/him

English

90% Melbourne, Australia - 10% Larissa, Greece

CreditAttribution: klonos commented 1 February 2012 at 15:09

...has this point ever been raised?

In fact yes, but for different reasons (this specific maintainer thinks that "...dictating how people write the names of their modules is ridiculous").

And if so, what is the thinking as to why the other method was selected?

...you might want to follow #1346158: Decide on coding standard for capitalization of module names [policy, no patch]

As I've already said in the other issue:

...this issue is about using Coder in order to "enforce" a policy that is already in place ... file a new issue about removing that policy from drupal coding standards.

Comment #3

richardp CreditAttribution: richardp commented 1 February 2012 at 15:23

I think I will get involved too, then. I understand if this capitalization scheme is important for consistency, but I honestly believe it hurts readability and adds to confusion, as I pointed out in my examples above.

Thank you for bringing it to my attention in any event. I'm honestly not trying to go to war over this (I really have more important things in my life than worrying about a capital letter ;), but I'd like the chance to discuss this issue with other people before making this change.

Thanks again,
Richard

Comment #4

klonos

he/him

English

90% Melbourne, Australia - 10% Larissa, Greece

CreditAttribution: klonos commented 2 February 2012 at 00:39

Status:

Active

» Postponed

Fair enough Richard. Setting this to "postponed" then.

Comment #5

Michelle

she/her

English

Wisconsin, USA

CreditAttribution: Michelle commented 2 February 2012 at 04:34

In fact yes, but for different reasons

Actually, no, it was for the same reason. Yes, I also think it's ridiculous to tell people how to name their projects but my bigger concern is that our current standard is enforcing incorrect English by insisting that proper names are sentence cased.

Michelle

Comment #6

klonos

he/him

English

90% Melbourne, Australia - 10% Larissa, Greece

CreditAttribution: klonos commented 2 February 2012 at 14:30

Actually, no, it was for the same reason...

I honestly don't see how Richard's polite and well-put examples that demo the problem are the same with the "It is ridiculous - it's my baby - I'll call it however I like - screw the standards" statement Michelle. As I've already discussed this matter with you previously, you seem to be a tad too ...how should I put this nicely here without getting you started? ...Jumpy?

To prove my point I'll simply emphasize on the fact that neither your comment nor my reply really belong here. We are both off-topic, but since you felt you had to "defend" yourself after my comment in #2, I'll take the first step and apologize. I didn't mean it that way. Perhaps I should have said something like:

"Very nice examples Richard! Perhaps you should post them at #1346158: Decide on coding standard for capitalization of module names [policy, no patch] because nobody else has made that point before there."

Does that calm you down? If not, I'll have to try buying you beer or whatever you please. So... friends??? ;)

I've already stated that I believe that the standard should be changed to allow project owners to call their projects whatever they like. It was placed there a long time ago and I guess it was because we wanted to prevent people from using something like "VERY VERY COOL PROJECT" as a name.

PS: sorry for "polluting" your issue queue and mailbox Richard :/

Comment #7

Michelle

she/her

English

Wisconsin, USA

CreditAttribution: Michelle commented 2 February 2012 at 15:08

Well, when you take one quote out of context and completely ignore my continuing argument that, if we are going to have a standard, it should standardize on correct English, yeah, I'm going to defend myself. To say that no one has put forth the argument before just underscores the fact that you didn't read past my annoyance at having someone come into my queue and tell me I need to "fix" something that isn't broken.

Anyway, I'm done being OT now. The rest can be said in that issue.

Michelle