[wp-meta] [Making WordPress.org] #6600: Update Language Suggest text

[Making WordPress.org]

#6600: Update Language Suggest text
--------------------------------+--------------------
 Reporter:  dd32                |      Owner:  (none)
     Type:  defect (bug)        |     Status:  new
 Priority:  normal              |  Milestone:
Component:  WordPress.org Site  |   Keywords:
--------------------------------+--------------------
 ''follow up from #6599''

 Currently the homepage language guess text uses these:
  - (singular) WordPress is also available in %s.
  - (multiple) WordPress is also available in %s (also %s).

 Support Forums use:
  - (singular) WordPress support forums are also available in %s.
  - (multiple) WordPress support forums are also available in %s (also %s).

 Plugins use this:
  - (singular) The plugin directory is also available in %s.
  - (multiple) The plugin directory is also available in %1$s (also: %2$s).
  - (singular) This plugin is also available in %1$s. <a href="%2$s">Help
 improve the translation!</a>
  - (multiple) This plugin is also available in %1$s (also: %2$s). <a
 href="%3$s">Help improve the translation!</a>


 Feedback suggests that the `(also ...)` part is probably not ideal, and in
 addition the plugin directory uses `also:` rather than just `also`.

 These strings should probably be updated to read:
 > WordPress is also available in {locale}, {locale2}, and {locale3}.

 That would be "one" string, so we should update our strings from `__()` to
 `_n()` as well, and respect the locale's `wp_sprintf_l()` translations for
 how to join those locale names, rather than just using `,`.

 This would also help with the display of English variants which have
 brackets in their name (IMHO these are named incorrectly, but that's a
 different issue):
 > WordPress is also available in English (Australia) (also English (UK)).

 H/t Javi

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/6600>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org