Wordpress -> WordPress in core?

[MiroslavGlavic]

I view this as calling my dad by his first name, technically I can do it but out of respect I call him dad/father.

Why can't people respect WordPress? Isn't the trademark WordPress and not Wordpress? freedoms have limits.

My freedom of expression (freedom of speech in the US) ends where someone else's begin.

[Rarst]

Why can't people respect WordPress? Isn't the trademark WordPress and not Wordpress? freedoms have limits.

So no matter how respectful you are towards WordPress you deserve to have your links broken, because someone needed to scratch an itch and felt there isn't enough respect.

That is opposite of respect.

[chipbennett]

I view this as calling my dad by his first name, technically I can do it but out of respect I call him dad/father.

Why can't people respect WordPress? Isn't the trademark WordPress and not Wordpress? freedoms have limits.

My freedom of expression (freedom of speech in the US) ends where someone else's begin.

This has nothing to do with respect or trademark.

Forcing correct capitalization (or not) has no bearing on defending one's trademark. Spelling "Microsoft" as "MicroSoft" or "Micro$oft" (or "iPhone" as "IPhone" or "iphone") does not inherently violate trademark - nor does failure to attempt to prohibit such uses dilute one's trademark.

By the way: the WordPress trademark is enforced for top-level domain names, which are case-insensitive. WordPress would claim trademark rights to usage of www.mywordpressdomain.com - even though this usage is all-lower-case.

And technically speaking, the registered word mark actually consists of "WordPress" in small-caps, not CamelCase. So, pretty much everyone in existence has been violating the *actual* word mark, by not using small-caps.

The WordPress trademark is not impacted by spelling or capitalization.

As for respect and freedom of expression: trademark law does not abridge one's right to "disrespect" an entity by mis-spelling (or, mis-capitalizing) their trademark. Further, mis-capitalizing WordPress is not necessarily an act of disrespect for either the project or the trademark.

Likewise, if one chooses to express himself in such a manner, such expression in no way abridges anyone else's right or ability of self-expression - including Automattic (owner of the WordPress trademark) or the WordPress Foundation (eventual owner of the trademark).

[chipbennett]

Oh, and then there's this little gem from the actual certificate of registration:

"The mark consists of standard characters without claim to any particular font, style, size, or color."

[Ryan]

Oh, and then there's this little gem from the actual certificate of registration:

"The mark consists of standard characters without claim to any particular font, style, size, or color."

Do you know if that only applies to registered trademarks, or is that also a rule for trademarks in general?

[davecoveney]

I'm keeping relatively quiet on this one because truth is, I've given up caring. Matt and those who believe he speaks only The Truth will continue to do whatever they feel is for the best, and any other opinion missed the point.

There's no point arguing, really - everyone's tried that.

So we can just wait for the long slow slide into the trough of disillusionment, at which point a fork or two may happen. The fork may or may not be more successful, but it'll no doubt be different.

[JohnM]

The smart move would be to make it possible to turn off the function in the write settings.

options-writing.png

[Jeffro]

Then I'd be even more upset because post revisions ui to control how that feature works will never see the light of day. If this got some ui treatment, I'd be livid.

[Martin]

Interesting feature, I have no issues with the word WordPress being corrected. I always type it the right way anyway.

The feature WordPress spell check is flawed anyway...

Does not correct the following:

wOrDpReSs
wordpress

Seems to only correct Wordpress...

[chipbennett]

The feature WordPress spell check is flawed anyway...

Does not correct the following:

wOrDpReSs
wordpress

Seems to only correct Wordpress...

According to comments on Trac, that is by design/intention.