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

 There's a misunderstanding I think. First my initial proposition is not to
 consider a "generic" language file but eventually to consider one of the
 locale to be the default for one given language, like es_ES would be the
 default if a es_MX file is not present. You do that by providing a es file
 (renaming the es_ES.mo file to es.mo)

 Second there's no asking other people to change what they do (including WP
 translators) if they don't want. But including that fallback mechanism
 would allow me (and others) to provide a unique language file for all
 locales of that language without the user doing anything (they can still
 define es_MX and get MX locale when available), me having to copy the same
 file over with a different name (like es_ES, es_MX, es_CL, es_PE, es_VE,
 etc.) or adding the code I described here: http://vedovini.net/2013/12
 /smart-fallback-mechanism-for-loading-text-domains-in-wordpress/

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