WordPress.org
Get WordPress

Making WordPress.org

Opened 6 months ago

Closed 6 months ago

#8035 closed enhancement (reported-upstream)

Bug Report and Improvement Suggestions for Learn WordPress Localization Strings and Link Behavior

Reported by: kimjiwoon's profile kimjiwoon Owned by:
Milestone: Priority: normal
Component: International Sites (Rosetta) Keywords: has-patch
Cc:

Description

### Title: Bug Report and Improvement Suggestions for Learn WordPress Localization Strings and Link Behavior

#### Summary

While reviewing the Korean localization status of learn.wordpress.org and wordpress.org, several issues were identified: inconsistent translation strings, link behaviors that appear to be bugs, and opportunities for significant user experience improvements.

### 1. Bug: Incorrect Polyglots Team Link in Rosetta Site Footer

There is a bug in the global footer of Rosetta sites where the language name link does not direct users to the correct language team page.

  • Observed Behavior:
    • On the Korean Rosetta site (ko.wordpress.org), clicking the language name '한국어' in the footer leads to the general Polyglots team listing page (https://make.wordpress.org/polyglots/teams/) instead of the specific Korean team page.
  • Expected Behavior:
    • The link should direct users to the Korean translation team’s dedicated page (https://make.wordpress.org/polyglots/teams/?locale=ko_KR).
  • Steps to Reproduce:
    1. Visit https://ko.wordpress.org.
    2. Scroll to the bottom footer.
    3. In the language list next to the WordPress logo, click the '한국어' link.
    4. Check the resulting URL.
  • Impact:
    • This increases the difficulty for Korean users who wish to contribute to translations, as it makes finding their language team less intuitive.

### 2. Improvement Proposal: Multilingual UI Support on the Main wordpress.org Site

It is proposed that the main wordpress.org site adopt the same localized UI (header/footer) functionality via the ?locale parameter as already available on learn.wordpress.org.

  • Background:
    • Currently, Rosetta site footers (such as ja.wordpress.org or ko.wordpress.org) link to learn.wordpress.org with the appropriate ?locale parameter, offering a localized UI.
    • This shows that learn.wordpress.org is capable of providing a multilingual UI via the locale parameter.
    • However, the main wordpress.org site does not offer this dynamic UI translation unless users visit a Rosetta site.
  • Proposal:
    • Enable the main wordpress.org site to recognize the ?locale parameter and dynamically display core UI elements (global header/footer) in the selected language.
    • This would allow users to browse global information on wordpress.org in their preferred language interface, independent of the community-driven Rosetta sites.
  • Expected Benefits:
    • Improved accessibility for users worldwide.
    • Enhanced user experience by allowing separation of UI language and content language (which is mainly English).

### 3. Reference: Inconsistency in "Learn WordPress" String Management

The key brand term "Learn WordPress" is distributed across multiple translation projects, making consistency difficult to maintain.

---

Change History (2)

This ticket was mentioned in ​PR #703 on ​WordPress/wporg-mu-plugins by ​@dd32.
6 months ago #1

  • Keywords has-patch added

The existing footer links to the Polyglots teams page, but it should link to the specific locale teams page instead.

See https://meta.trac.wordpress.org/ticket/8035

#2 @dd32
6 months ago

  • Resolution set to reported-upstream
  • Status changed from new to closed

Hello @kimjiwoon,

In future, please keep issues to a single issue per ticket.

  1. Bug: Incorrect Polyglots Team Link in Rosetta Site Footer

Seems reasonable, I've submitted a PR to the footer here:
​https://github.com/WordPress/wporg-mu-plugins/pull/703

This should've been reported as a ticket to the above repo for the Footer block, as such, this item would've been either fixed upstream and closing this ticket, or redirected there and closed as reported-upstream.

  1. Improvement Proposal: Multilingual UI Support on the Main wordpress.org Site

Yeah, we agree, we'd love to get rid of all of the Rosetta sub-sites and their customisability.

This isn't on the roadmap at present though. Subdomains also offer a higher level of flexibility.

This ticket would be closed as maybelater for now.

  1. Reference: Inconsistency in "Learn WordPress" String Management

Yes, it's well known that translators can translate things differently between repo's, the Translation memory and Translation consistency tools are designed to help Translators to resolve this.

You should discuss it within the Korean translation managers if you're translating things differently between different projects.

Once you come to an agreement, you can update the existing translations.

You can use the Translation consistency tool to find the various string forms:
​https://translate.wordpress.org/consistency/?search=Learn+WordPress&set=ko%2Fdefault&project=

For project management reasons, WordPress translation reasons, and Gettext reasons, we can't realistically use a centralised translation string for this.

This ticket would be closed as reported-upstream by taking it to the korean translators, or wontfix/worksforme if you're asking for a code change.

Due to the mixed issues presented on this ticket (Affecting multiple 'projects'), this is going to get closed as reported-upstream as that was the only actionable item presented. The other issues may have warranted further discussion, but not on this ticket as it is.

Note: See TracTickets for help on using tickets.