[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  |  Resolution:
 Keywords:                      |
--------------------------------+---------------------

Comment (by dd32):

 > Should this endpoint be refactored to use the core REST API
 infrastructure? that seems like overkill, but could also be more future-
 dev-friendly (since we could use WP functionality as normal).

 The only blocker there is that this does some GeoIP stuff which leads to
 this being a very non-cache-friendly URI and loading WordPress is
 significantly more expensive processing wise than the existing PHP.

 You're correct that the translation system isn't loaded, core has a
 `wp_load_translations_early()` function which could be used with
 Multisites `SHORTINIT`, but unfortunately you can't switch to a arbritrary
 locale with that mode, as there's some WordPress components which don't
 work well with early loaded translations and SHORTINIT.

 [attachment:"6600.2.diff"] is [attachment:"6600.diff"] but with loading
 the translations for `wp_sprintf_l()` from the Core GlotPress project.

 @ryelle do you think that'd resolve the immediate needs here?

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