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

WordPress Trac noreply at wordpress.org
Mon Aug 17 18:48:00 UTC 2015


#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 ocean90):

 Replying to [comment:31 markoheijnen]:

 > Currently the implementation lacks detection if de_DE_formal is de_DE.
 Can you explain this? Why should de_DE_formal be de_DE?

 > 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.
 What do you mean by "styling"? I'm managing a lot of business sites where
 WordPress *and* the content is formal. But not sure why this should be
 specific to German.

 > So for a plugin like Babble de_DE would be enough in this case.
 Maybe, but this needs to be handled by Babble. Babble doesn't need to
 support each language if the developers think that some can be ignored.

 > My opinion is that formal German is a writing style purely because it's
 still the same German as de_DE but more formal.
 It's still a variant and that's what this ticket is about.

 > Because of that I believe it is hacking locales. BCP47 is about the
 length of a the locale.

 BCP 47 is about '''Tags for Identifying Languages''' and is referenced by
 the W3C for the `lang` attribute, see http://www.w3.org/TR/html5/dom.html
 #attr-lang.

 This ticket isn't primary about formal vs informal. It's about supporting
 ~70 variant subtags.

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


More information about the wp-trac mailing list