[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:  ocean90
     Type:  task (blessed)                |      Status:  closed
 Priority:  normal                        |   Milestone:  4.3
Component:  I18N                          |     Version:
 Severity:  normal                        |  Resolution:  fixed
 Keywords:  has-patch meta needs-testing  |     Focuses:
------------------------------------------+----------------------

Comment (by markoheijnen):

 I'm wondering if the current solution is the right one. We currently
 hacking the locale to support formal/informal. Informal/Formal is a
 writing style rather then a dialect. Personally I rather see it as a
 separate field so that get_locale() is still the same.

 You can already see the problem with the commit made. CSS had to be
 changed and plugins like Babble need to do more work. For user content and
 plugins they care mostly about that it's German so de_DE. The only reason
 I see we need this is that we get the right language package. Then having
 the style as a separate option could be a better solution. Then there is
 no change of breakage.

 Reason about this is that I would like to split the locale from the style.
 Knowing what the right GlotPress project will be.

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