[wp-trac] [WordPress Trac] #28303: How to handle default/formal translations for automatic upgrades?

[WordPress Trac]

#28303: How to handle default/formal translations for automatic upgrades?
-------------------------+------------------
 Reporter:  zodiac1978   |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  4.3
Component:  I18N         |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+------------------

Comment (by ocean90):

 [attachment:28303.5.patch] removes the language code extraction
 completely. The reason for this is that for example `pt-PT-ao1990` is a
 valid value for the lang attribute. It looks like `formal` and `informal`
 aren't valid sub tags yet, so we could make an exception for these
 locales. But since the lookup process includes a fallback pattern (BCP47,
 section 4.3) we actually don't need this.

 Language tags are defined in [https://tools.ietf.org/html/bcp47 BCP47].
 All valid sub tags are listed on [http://www.iana.org/assignments
 /language-subtag-registry/language-subtag-registry this page] or as a
 [https://r12a.github.io/apps/subtags/ web app here].

--
Ticket URL: <https://core.trac.wordpress.org/ticket/28303#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform