[wp-meta] [Making WordPress.org] #8035: Bug Report and Improvement Suggestions for Learn WordPress Localization Strings and Link Behavior

[Making WordPress.org]

#8035: Bug Report and Improvement Suggestions for Learn WordPress Localization
Strings and Link Behavior
-------------------------------------------+-------------------------------
 Reporter:  kimjiwoon                      |       Owner:  (none)
     Type:  enhancement                    |      Status:  closed
 Priority:  normal                         |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:  reported-
 Keywords:  has-patch                      |  upstream
-------------------------------------------+-------------------------------
Changes (by dd32):

 * status:  new => closed
 * resolution:   => reported-upstream


Comment:

 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`.

 > 2. 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.

 >  3. 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.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/8035#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org