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

 I attached an updated patch that implements @cvedovini idea.  I was trying
 to work within the existing framework for translations- but a generic
 fallback could work better.

 1)  Translation teams from different locales could focus on the generic
 fallback version first- and then quickly copy it to make country specific
 localizations.  Hopefully it would not get political as any translator who
 disagreed with a translation in the default could just change it for their
 specific locale.

 2)  This avoids having to build and maintain and ordered list of fallbacks
 for each language.

 Instead of defaulting to "generic" we could default to the locale with
 simply the largest population.  E.g. English > United States, Spanish >
 Mexico, Portuguese > Brazil.  But then you might get might get a Spanish
 (es_ES) translation for an es_MX localizations simply because it would be
 used more.  So for this reason, a generic fallback would probably be
 better.

 Thanks for the coding tip @toscho.  I am using that instead for this
 updated patch.

 Nacin, could you outline where the performance issues are?  (I don't have
 much experience in that area).  Would it be helpful cache translation file
 paths in a transient?

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