WordPress.org

Make WordPress Core

Opened 5 years ago

Last modified 2 months ago

#38913 reviewing enhancement

Aggregation of contracted and not contracted verb forms (cannot, doesn't)?

Reported by: Presskopp Owned by:
Milestone: 6.0 Priority: normal
Severity: normal Version: 4.7
Component: Administration Keywords: good-first-bug has-patch has-unit-tests
Focuses: ui-copy Cc:

Description

I count

18x does not vs. 5x doesn't
28x cannot vs. 4x can not vs. 1x can't (+ 1x in 'administration')
lots of is not vs 1x isn't

Do we want to combine them?

Attachments (3)

38913.patch (27.9 KB) - added by aandrewdixon 3 years ago.
Patch changes "can not" and "can't" to "cannot", "doesn't" to "does not" and "isn't" to "is not".
38913.2.patch (79.1 KB) - added by aandrewdixon 3 years ago.
Trying again as my first attempt somehow missed the whole wp-includes directory when I was searching, plus I found some other words like haven't, couldn't, etc... that needed changing as well.
38913.diff (136.4 KB) - added by audrasjb 2 months ago.
patch refreshed against trunk

Download all attachments as: .zip

Change History (39)

#1 @ramiy
5 years ago

Related: #39176

#2 @desrosj
3 years ago

  • Keywords needs-patch good-first-bug added
  • Milestone changed from Awaiting Review to Future Release

#3 @Presskopp
3 years ago

@desrosj What is the decision? What forms of expression would we use preferrably?

#4 @socalchristina
3 years ago

Hi @Presskopp. I see in
ticket:39176#comment:4 that the preferred form of expression is to replace doesn't contraction with does not. Is that the consensus on contractions @desrosj? I'm happy to work on this but I don't see a reference to the particular file.

#5 @aandrewdixon
3 years ago

Personally, I think the non-contracted verb form is much clearer, particularly for people were their first language is not English but they are using an English install for whatever reason.

@aandrewdixon
3 years ago

Patch changes "can not" and "can't" to "cannot", "doesn't" to "does not" and "isn't" to "is not".

@aandrewdixon
3 years ago

Trying again as my first attempt somehow missed the whole wp-includes directory when I was searching, plus I found some other words like haven't, couldn't, etc... that needed changing as well.

#6 @Mista-Flo
3 years ago

  • Keywords has-patch added; needs-patch removed

#7 @Presskopp
2 years ago

Do not you ..

should be avoided, if you ask me

#8 @garrett-eclipse
2 years ago

  • Component changed from Text Changes to Administration
  • Focuses ui-copy added

This ticket was mentioned in Slack in #core by francina. View the logs.


8 months ago

#10 follow-up: @francina
8 months ago

The ticket was mentioned during the new contributors chat on May 26th. The contracted verbs mentioned by the original reporter are probably not the only ones.
I suggest we make a list of all the possible contractions we should be looking for in the source code and evaluate which ones have to be "searched and replaced" and which ones should stay as contracted forms. As mentioned by @Presskopp "Do not you" is not a better option than "Don't you".

Top of my mind: potential contracted versions of "to be" (I'm, You're, Isn't it, etc...), to have (haven't), and can/could as mentioned by @aandrewdixon.

Does anyone else have any input on this? If you do, please leave your comment. Thanks!

#11 in reply to: ↑ 10 @SergeyBiryukov
8 months ago

Replying to francina:

I suggest we make a list of all the possible contractions we should be looking for in the source code and evaluate which ones have to be "searched and replaced" and which ones should stay as contracted forms.

When searching the core, make sure to also look for apostrophes encoded as numeric entities, e.g. doesn’t in addition to doesn't.

This ticket was mentioned in PR #1310 on WordPress/wordpress-develop by jeffpaul.


8 months ago

  • Keywords has-unit-tests added

This PR makes the following changes in expanding encoded contractions into its composite words:

  • doesn’t > does not
  • can’t > can not
  • won’t > will not
  • couldn’t > could not
  • don’t > do not
  • isn’t > is not
  • haven’t > have not
  • aren’t > are not
  • wasn’t > was not
  • we’re > we are
  • there’s > there is
  • I’m > I am
  • you’re > you are
  • you’d > you would

Note that this PR does NOT make changes of cannot to can not as I was not certain that was really helpful, but can amend the PR to make those changes if desired.

Similarly this PR does not change un-encoded contractions into its composite words (e.g., doesn't > 'does not') as many of those code comments and there are LOTS of them, but again is that is desired then I can amend the PR to include those changes as well.

Trac ticket: https://core.trac.wordpress.org/ticket/38913

#13 @JeffPaul
8 months ago

  • Keywords needs-copy-review added; has-unit-tests removed

#14 @JeffPaul
8 months ago

  • Milestone changed from Future Release to 5.9

This ticket was mentioned in Slack in #core by francina. View the logs.


7 months ago

#16 @audrasjb
4 months ago

  • Keywords needs-refresh added

There are some conflicts in the proposed PR, so I'm adding needs-refresh workflow keyword.

This ticket was mentioned in Slack in #core by audrasjb. View the logs.


3 months ago

#18 @audrasjb
3 months ago

  • Keywords needs-copy-review removed

As per today's bug scrub:

This ticket is still a good candidate for 5.9, but we need a committer to finish the work, as the patch need to be committed soon after the refresh to avoid new conflicts (76 files are impacted by this patch).

This ticket was mentioned in Slack in #core by audrasjb. View the logs.


3 months ago

This ticket was mentioned in Slack in #core by audrasjb. View the logs.


3 months ago

@audrasjb
2 months ago

patch refreshed against trunk

This ticket was mentioned in Slack in #core by audrasjb. View the logs.


2 months ago

#22 @hellofromTonya
2 months ago

  • Keywords needs-refresh removed
  • Owner set to hellofromTonya
  • Status changed from new to reviewing

This ticket was mentioned in PR #1840 on WordPress/wordpress-develop by audrasjb.


2 months ago

  • Keywords has-unit-tests added

#24 @audrasjb
2 months ago

New PR available for review ☝️

This ticket was mentioned in Slack in #core by audrasjb. View the logs.


2 months ago

#26 @prbot
2 months ago

hellofromtonya commented on PR #1840:

@audrasjb the tests are failing as the strings changed. Mary Baum is reviewing the string changes to help me out. Once she's done and it's all okay, then the tests can be updated to match.

This ticket was mentioned in Slack in #core by hellofromtonya. View the logs.


2 months ago

#28 @audrasjb
2 months ago

PR refreshed @hellofromTonya. Tests are passing now.
I didn't include the proposed string changes are they are changing qunit strings (those are internal strings)

#29 @audrasjb
2 months ago

  • Keywords commit added

#30 @prbot
2 months ago

audrasjb commented on PR #1840:

@audrasjb the tests are failing as the strings changed. Mary Baum is reviewing the string changes to help me out. Once she's done and it's all okay, then the tests can be updated to match.

PR refreshed :)

#31 @hellofromTonya
2 months ago

@audrasjb I'm not seeing the changes Mary Baum did, such as cannot instead of can not. Are those to be included in this commit?

#32 @audrasjb
2 months ago

@hellofromTonya maybe I'm misleading, but the diff file proposed by Mary was addressing strings used in unit tests so as I commented in the related thread, I'm not sure it's worth replacing these qunit sample sentences (they could be lorem ipsum text as well).
For reference: https://wordpress.slack.com/archives/C02RQBWTW/p1636425668068900

This ticket was mentioned in Slack in #core by hellofromtonya. View the logs.


2 months ago

#34 @audrasjb
2 months ago

  • Keywords commit removed
  • Milestone changed from 5.9 to Future Release

Given the huge perimeter of this change (see this Trac thread https://wordpress.slack.com/archives/C02RQBWTW/p1636501241200000), the decision is to move this change to Future release, hopefully to early 6.0.

Removing commit for now.

#35 @SergeyBiryukov
2 months ago

Might be relevant for when the ticket gets picked up again:
Cannot, Can Not or Can’t—Which Should I Use? | Grammarly:

Don’t use can not when you mean cannot. The only time you’re likely to see can not written as separate words is when the word “can” happens to precede some other phrase that happens to start with “not”:

  • Example: We can not only break even, but also turn a profit.
  • Example: The company’s new product can not only reduce emissions, but also trap some of the existing greenhouse gasses.

Here is a quick summary:

  • Can’t is a contraction of cannot, and it’s best suited for informal writing.
  • In formal writing and where contractions are frowned upon, use cannot.
  • It is possible to write can not, but you generally find it only as part of some other construction, such as “not only . . . but also.”

#36 @hellofromTonya
2 months ago

  • Milestone changed from Future Release to 6.0
  • Owner hellofromTonya deleted

Hey 6.0 is now available. Moving it into 6.0. Removing myself as the reviewing as there's more work to be done before it's ready for commit.

Note: See TracTickets for help on using tickets.