[wp-trac] Re: [WordPress Trac] #9794: Continent/city translations

[WordPress Trac]

#9794: Continent/city translations
-----------------------------------+----------------------------------------
 Reporter:  Denis-de-Bernardy      |        Owner:  ryan  
     Type:  defect (bug)           |       Status:  closed
 Priority:  normal                 |    Milestone:  2.8   
Component:  Date/Time              |      Version:  2.8   
 Severity:  normal                 |   Resolution:  fixed 
 Keywords:  has-patch 2nd-opinion  |  
-----------------------------------+----------------------------------------

Comment(by xibe):

 Replying to [comment:10 Denis-de-Bernardy]:
 > doesn't the translation tool make the strings default to their english
 value?

 It depends on the tool I guess, but when updating the PO to the latest
 trunk POT in poEdit, it does the following:
   - put around 270 cities strings as new/not translated - ergo, if not
 translated, WP will display them as-is;
   - put around 180 cities strings as fuzzy - that is, it has tried to
 match the strings with other already translated strings, and it's up to
 you to make sure the match is adequate.

 For instance, with the current fr_FR PO, it gives these fuzzy
 translations:
   - Algiers -> lignes
   - Dar es Salaam -> Marquer comme indésirable
   - San Luis -> Chercher dans les liens
   - Baku -> Sauvegarde de sécurité

 And so on...

 Obviously, not everyone uses a fuzzy-making tool such as poEdit, but it's
 enough to make translation a must-do. WordPress does defaults to the
 original string if no translation is found, but since the fuzzy strings
 ARE translation, that means unless the translateur deletes all the
 fuzzies, he'll end up with weird translations in that form instead of the
 original string.

 Furthermore, for those who set their tool to not try to match fuzzy
 strings, they still have to deal with having these 500 cities strings
 untranslated in their PO. They'll be translating them sooner or later in
 order to get that number to zero - translator pride, y'know? :)

 Therefore, either the core devs do not allow these strings to be
 translated for anyone, or the translators have to translate them all, but
 there is no middle-ground here, I think.

 I, for one, vote for full-translation (ergo, the current status), even if
 it's gonna be a real pain in the neck to check them all up...

 This should probably be decided in the wp-polyglots list. Nikolay, care to
 launch the subject? We can have a PollDaddy vote ;-)

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/9794#comment:11>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software