WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 5 years ago

#9974 closed enhancement (wontfix)

Text tweak for option in Text widget

Reported by: demetris Owned by:
Milestone: Priority: normal
Severity: minor Version: 2.8
Component: UI Keywords: has-patch tested
Focuses: Cc:

Description

The patch replaces this:

Automatically add paragraphs.

with this:

Auto-paragraphing

Attachments (1)

t9974-text-widget-text-tweak.diff (1015 bytes) - added by demetris 5 years ago.
Replaces “Aumatically add paragraphs.” with “Auto-paragraphing” in Text widget option

Download all attachments as: .zip

Change History (11)

demetris5 years ago

Replaces “Aumatically add paragraphs.” with “Auto-paragraphing” in Text widget option

comment:1 Denis-de-Bernardy5 years ago

  • Component changed from General to UI
  • Milestone changed from 2.8 to 2.9

string freeze

comment:2 mrmist5 years ago

-1 to this patch as I dislike the grammar. I feel that it's a step backwards.

comment:3 Denis-de-Bernardy5 years ago

  • Milestone 2.9 deleted
  • Resolution set to wontfix
  • Status changed from new to closed

me too... let's just close.

comment:4 follow-up: demetris5 years ago

  • Milestone set to 2.9
  • Resolution wontfix deleted
  • Status changed from closed to reopened

What’s wrong with the grammar? “Paragraph” is perfectly common as a verb, and “to auto-paragraph” is used often for this kind of operation.

For “paragraph” as a verb, see:

<http://www.thefreedictionary.com/paragraph>

The New Shorter Oxford English Dictionary (probably the finest English dictionary in digital form) gives as second sense of the verb:

“Divide into or arrange in paragraphs.”

It also says that this usage is recorded since the 18th century. (L18: late 18th)

The current string:

First, is *too long* for this space.

Second, and strictly speaking, is not accurate: The option does not add paragraphs. It replaces double line-breaks with p elements (which is too technical for a UI string), or, in other words, it *separates* text into paragraphs.

Please reconsider this.

By the way, how do we know that we are in a string freeze? Is this announced somewhere? (I thought strings got frozen in the first RC.)

comment:5 dd325 years ago

The grammar makes sense to me (Probably because i'm non-US). However, I'm not too sure how the majority of the world would understand "Auto-Paragraphing".

As for string freeze, Like everything in WordPress Development, There is no definite line, However, A few other changes have been set back for that same reason, So..

Its virtually when we're at a point thats close to release, In my time with WordPress, The stages from the final beta (who knows which one it'll be...) to RC's to Release can be as small as a day or 2, Mid-beta seems to be the best string-freeze time around here.

comment:6 westi5 years ago

String freeze happens during beta, we need to give translators enough stability to do the translation so they do not have to lag far behind the english release.

Especially now we have the builtin upgrader with language awareness.

comment:7 in reply to: ↑ 4 mrmist5 years ago

Replying to demetris:

What’s wrong with the grammar? “Paragraph” is perfectly common as a verb, and “to auto-paragraph” is used often for this kind of operation.

To be fair, I didn't say that there was anything wrong with the grammar, I said that I disliked it. I don't believe that changing things into verbs is a particularly friendly construct in every event, and in this case I don't believe that using "auto-paragraphing" would be any more descriptive of what happens than the existing text. (Neither is true IMO).

Equally I'm not convinced that the existing text is too long for the space. There is still plenty of white space around it in my view. Maybe if you have a tiny screen, but the box is pretty wide anyway.

If I were going to change this text to anything, it would probably be "Keep line breaks."

comment:8 follow-up: demetris5 years ago

@Peter: Yes. On the other hand, it doesn’t make sense freezing strings when the UI is still fluid. See, e.g.:

http://core.trac.wordpress.org/changeset/11445

This will be in Beta 3 or RC 1, whatever comes next.

It would be good to have an official schedule for this. For one thing, it would save resources. (For example, this patch I submitted here may be irrelevant in 6 months.)

Or, if not an official schedule, then something like this:

  1. There is always a Beta 2 and strings freeze when Beta 2 is released.
  1. There is always at least 2 weeks time between Beta 2 and final release.

@mrmist:

This has nothing to do with the current annoying trend of verbing nouns even when a verb already exists. “To paragraph” is established usage, centuries old.

That said, I like your “Keep line breaks” better. But it’s not descriptive of what the option does.

comment:9 in reply to: ↑ 8 westi5 years ago

Replying to demetris:

@Peter: Yes. On the other hand, it doesn’t make sense freezing strings when the UI is still fluid. See, e.g.:

http://core.trac.wordpress.org/changeset/11445

That was 6 days ago and has already been in multiple nightly drops to which the translators can upgrade using the built in upgrader.

I pushed for a string freeze after this change had been made.

It would be good to have an official schedule for this. For one thing, it would save resources. (For example, this patch I submitted here may be irrelevant in 6 months.)

Or, if not an official schedule, then something like this:

  1. There is always a Beta 2 and strings freeze when Beta 2 is released.
  1. There is always at least 2 weeks time between Beta 2 and final release.

Yes we need a clearer schedule. This isn't the right place to discuss it though.

comment:10 ryan5 years ago

  • Milestone 2.9 deleted
  • Resolution set to wontfix
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.