[wp-trac] [WordPress Trac] #28197: Fallback Languages

[WordPress Trac]

#28197: Fallback Languages
---------------------------+------------------------------
 Reporter:  downstairsdev  |       Owner:
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  I18N           |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------

Comment (by grapplerulrich):

 I am not sure a generic language fallback is best. I think you are best
 asking on the [http://make.wordpress.org/polyglots/ Polyglots] make blog.

 Who defines what is the generic form? Take the spelling of colour/color in
 English. How can you convince both parties that which is the most generic
 form? If we say for the sake of argument that the en_US form is more
 generic then we could just have en_UK fallback to en_US.
 (I know there is no en_US translation file. This is just an example that
 most should be able to understand.)

 I was told by @jenialaszlo at WordCamp Switzerland that Ukrainian could
 use a fallback to Russian. You would need to take that into account also.

 By introducing a generic file, it creates extra work for core translators
 and also theme/plugin translators/developers who would need to create a
 generic file so to make use of this new feature.

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