WordPress.org

Make WordPress Core

Opened 7 years ago

Closed 5 years ago

#29749 closed defect (bug) (wontfix)

Merge help text for widgets

Reported by: pavelevap Owned by: SergeyBiryukov
Milestone: Priority: normal
Severity: normal Version: 4.0
Component: I18N Keywords: has-patch
Focuses: Cc:

Description

We can save translators some work when combining one string (very similar help text) for widgets and widget panel in Customizer. See attached patch.

Attachments (1)

widgets_help.patch (1.9 KB) - added by pavelevap 7 years ago.

Download all attachments as: .zip

Change History (6)

#1 @MikeHansenMe
6 years ago

  • Keywords has-patch added

#2 @SergeyBiryukov
6 years ago

We would still have three different strings, even four if one of the merged strings changes in the future, but not the other.

#3 @pavelevap
6 years ago

Yes, main purpose was not to translate same sentence twice. Now we have:

Widgets are independent sections of content that can be placed into widgetized areas provided by your theme (commonly called sidebars).

and

Widgets are independent sections of content that can be placed into any widgetized area provided by your theme (commonly called sidebars). To populate your sidebars/widget areas with individual widgets, drag and drop the title bars into the desired area. By default, only the first widget area is expanded. To populate additional widget areas, click on their title bars to expand them.

I thought that we can split long string, so it can be translated only once and used for both places. It would make sense, because first sentence in help tab is very common and can be used as separate paragraph (as in Customizer).

#4 @afercia
6 years ago

  • Milestone changed from Awaiting Review to 4.5
  • Owner set to SergeyBiryukov
  • Status changed from new to assigned

Patch still applies and makes sense to me. Would defer to @SergeyBiryukov ​judgment :)

#5 @ocean90
5 years ago

  • Milestone 4.5 deleted
  • Resolution set to wontfix
  • Status changed from assigned to closed

I agree with comment:2 and going with a wontfix here.

Note: See TracTickets for help on using tickets.