[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):

 Replying to [comment:17 simonwheatley]:
 > Is it possible to use a more compact format for the variant suffix?

 There are official sub tags which are even longer than seven chars, for
 example `1694acad` in `fr-FR-1694acad`. BCP47 includes a section about
 [https://tools.ietf.org/html/bcp47#section-4.4 Length Considerations]
 which says, that there is no upper limit for language tags but "buffer
 sizes for language tags MUST allow for language tags of at least 35
 characters."
 So this sounds more like an implementation issues which needs to be fixed
 in the plugin, not something we have to consider if we want to support
 (official) variants of a languages.

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