[wp-trac] [WordPress Trac] #40244: Inconsistent casing in the list table select filters

[WordPress Trac]

#40244: Inconsistent casing in the list table select filters
-------------------------------------------------+-------------------------
 Reporter:  afercia                              |       Owner:
                                                 |  bhargavbhandari90
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  5.5
Component:  Administration                       |     Version:  5.4
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots good-first-bug has-  |     Focuses:  ui
  patch                                          |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * keywords:  has-screenshots good-first-bug has-patch commit => has-
     screenshots good-first-bug has-patch


Comment:

 I'd like to circle back to the question above asking for more information
 regarding sentence casing.

 In general, Core has been moving towards using sentence casing. This
 initiative has laregely stemmed from Gutenberg (which I believe should now
 be fully sentence cased), and has made its way into Core for consistency
 in a few locations. Here are some links for reference.

 - [https://developer.wordpress.org/block-editor/contributors/document
 /copy-guide/#five-pay-attention-to-capitalization Block Editor Handbook
 Copy Guide]
 - Related Gutenberg tickets:
 [https://github.com/WordPress/gutenberg/pull/18758 18758],
 [https://github.com/WordPress/gutenberg/issues/16764 16764],
 [https://github.com/WordPress/gutenberg/issues/19902 19902],
 [https://github.com/WordPress/gutenberg/issues/19900 19900],
 [https://github.com/WordPress/gutenberg/issues/12366 12366],
 [https://github.com/WordPress/gutenberg/pull/20187 20187],
 [https://github.com/WordPress/gutenberg/pull/19903 19903],
 [https://github.com/WordPress/gutenberg/pull/8927 8927],
 [https://github.com/WordPress/gutenberg/issues/8888 8888],
 [https://github.com/WordPress/gutenberg/issues/6210 6210],
 [https://github.com/WordPress/gutenberg/issues/4325 4325].
 - [47859] removes title case in favor of sentence case in Site Health.
 - #49616 exists to tackle the remaining title case instances in Core.
 - #49371 handled post labels.

 I thought that I had seen an issue that had a full breakdown of the
 benefits of sentence case vs. title case, but I can't seem to find what I
 remember. But #49616 has a good summary:

 > - Sentence case improves readability by allowing users to see proper
 shapes of words without the breaking flow of Capital Letters (i.e. Title
 Case is harder to read quickly because of how we typically read using the
 shapes of words.)
 > - Sentence case respects the difference between proper nouns and the
 other words. For example, “Upgrade to premium plan” vs. “Upgrade to
 Premium Plan” could have very different meanings.
 > - i18n: some languages capitalize different things (e.g. all nouns are
 capitalized in German). Title case adds cognitive load when users have to
 figure out which words are nouns, for example.

 At this point, regardless of personal preference, I think that there is
 too much momentum towards sentence case throughout Core to update the
 strings here to follow title casing. For the sake of consistency with
 other areas of the project that have already changed over fully, sentence
 casing should be used.

 If there arguments against title casing that have not been considered,
 this would warrant larger discussion across all aspects of the project
 being initiated through a Make Core post detailing why sentence casing is
 the wrong choice.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/40244#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform