Make WordPress Core

Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#37501 closed defect (bug) (fixed)

Localize plugin/theme directory links

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

Description

See the attached patch.

Localize https://wordpress.org/plugins/ and https://wordpress.org/themes/ links to allow translators to link to local plugin directories.

I want our hebrew users to link to https://he.wordpress.org/plugins/ and https://he.wordpress.org/themes/.

Attachments (1)

37501.patch​ (5.6 KB ) - added by ramiy 10 years ago.

Download all attachments as: .zip

Change History (9)

@ramiy
10 years ago

#1 @ramiy
10 years ago

  • Keywords has-patch added

This ticket was mentioned in ​Slack in #core-i18n by ramiy. ​View the logs.


10 years ago

#3 @SergeyBiryukov
10 years ago

  • Keywords i18n-change added
  • Milestone Awaiting Review → 4.6

Would love to see this in 4.6, as the theme directory doesn't have a locale banner (​#meta1864), and the current plugin directory doesn't have it either (the new one does, but there are some issues, see ​#meta1850).

Moving for consideration.

#4 @ocean90
10 years ago

  • Keywords i18n-change removed
  • Milestone 4.6 → Future Release

​As announced in yesterday's dev chat, RC is now only open for regressions. This is not a regression.

#5 @SergeyBiryukov
10 years ago

I thought the regressions rule only applies to code, and exceptions can be made for strings or docs. OK then :)

#6 @SergeyBiryukov
10 years ago

  • Milestone Future Release → 4.7

#7 @SergeyBiryukov
10 years ago

  • Owner set to SergeyBiryukov
  • Resolution → fixed
  • Status new → closed

In 38325:

I18N: Allow for WordPress Plugin/Theme Directory URLs to be localized.

Props ramiy.
Fixes #37501.

#8 @SergeyBiryukov
10 years ago

In 38953:

I18N: Allow for WordPress Plugin Directory URL in plugin details modal to be localized.

Props Soean.
Fixes #38495. See #37501.

Note: See TracTickets for help on using tickets.