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

 Thats what I tried but reopened the ticket since discussing this after 4.3
 is landed is pointless. Which is soon.

 Currently the implementation lacks detection if de_DE_formal is de_DE.
 That is an issue and gives the rights to reopen this ticket to rethink our
 current solution. It does break backwards compatibility even though it's
 purely styling. When writing content you will not write it in informal and
 formal but maybe that is different in Germany. So for a plugin like Babble
 de_DE would be enough in this case.

 My opinion is that formal German is a writing style purely because it's
 still the same German as de_DE but more formal. Because of that I believe
 it is hacking locales. BCP47 is about the length of a the locale.

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