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

 Replying to [comment:12 cvedovini]:
 > ...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.

 I'm sorry, but this is a recipe for disaster. Who gets to decide which one
 is the default? The es_ES translators? The es_MX ones? Whichever option
 you choose will inevitably raise a (probably nasty) discussion. Who will
 moderate that discussion (keeping in mind that it would be someone, who
 a)is qualified for that language and b)inevitably more familiar with one
 of the declinations)?

 > ...including that fallback mechanism would allow me (and others) to
 provide a unique language file for all locales of that language...

 Again, how will you provide that? Whose translation will it be? Will you
 be the one deciding which es_* is the generic one?

 Look, I don't mean to sound irascible and unwilling to compromise, but you
 are approaching this from an angle that's completely irrelevant to
 translators or native speakers of another language. I may be wrong, but
 this ticket seems to aim to solve a problem of the developers, **not** of
 the translators or native speakers. We couldn't care less about fallback
 languages; from our point of view, meaning no offense, it's a solution
 looking for a problem to solve.

 I would much rather see these efforts directed towards a procedure where a
 translator can easily and readily supply a **current** translation to a
 developer (instead of "oh, I'll include it in the next release", which is
 flawed), that we can trust that the code is properly gettexted and that
 .pot files are current with said code. Sadly, in 90% of the code I look
 at, this is most definitely **not** the case.

 Also see http://make.wordpress.org/polyglots/2014/05/12/hi-folks-we-
 started-a-conversation-about-fallback/#comment-251797

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