WordPress.org

Make WordPress Core

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#14043 closed defect (bug) (duplicate)

Remove capital_P_dangit

Reported by: harrym Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.0
Component: Formatting Keywords: capital_P_dangit
Focuses: Cc:

Description

While I understand that some may find other people's choice of case annoying, I think it's fair to say that the personal pedantries of WordPress's developers should not be formalised in the core.

That is to say: I think it's ok for people to spell WordPress however they like. Why is it reasonable for the core developers to force all authors using WordPress blogs to do it their way? What justification does this have other than to scratch a few personal itches?

WordPress's role is to provide a world-class publishing platform. Which it does very well. It is not WordPress's job to dictate editorial style, or to force all authors to follow Automattic's marketing guidelines.

See also several very sensible posts by hakre on #13583.

This filter should be removed for the next release. Patch attached, which would also solve #13971.

Attachments (1)

patch.diff (1.3 KB) - added by harrym 4 years ago.
Patch

Download all attachments as: .zip

Change History (7)

harrym4 years ago

Patch

comment:1 holizz4 years ago

  • Cc tom@… added

comment:2 filosofo4 years ago

  • Milestone Unassigned deleted
  • Resolution set to duplicate
  • Status changed from new to closed

I'm sympathetic. But proliferating tickets doesn't help anyone.

Matt Mullenweg is the WordPress project leader; he originated the change and has repeatedly defended it, so it's unlikely to change in the short term.

comment:3 harrym4 years ago

Do you have a link? Is he defending the capitalisation (perfectly understandabled) or forcing it on all WP users (indefensible)?

I haven't seen Matt or anyone else explain why this is justified.

comment:4 harrym4 years ago

(PS: I'm not proliferating tickets. I couldn't find a ticket saying we should get rid of it, or a patch to do so)

comment:5 mrmist4 years ago

#13971 is the current ticket discussing the issue.

comment:6 harrym4 years ago

Hmm, didn't notice that it has such recent replies. Thanks.

Note: See TracTickets for help on using tickets.