[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:  reopened
 Priority:  normal                 |    Milestone:  2.8     
Component:  Date/Time              |      Version:  2.8     
 Severity:  normal                 |   Resolution:          
 Keywords:  has-patch 2nd-opinion  |  
-----------------------------------+----------------------------------------
Changes (by demetris):

  * status:  closed => reopened
  * resolution:  fixed =>


Comment:

 @Denis:

 No.  Untranslated strings are empty in the PO file.  (The defaulting to
 the English/Whatever value must be happening either when the PO file is
 compiled into a MO file or when the application—WP here— reads the MO file
 and finds empty strings.  I haven’t checked.)

 @xibe:

 English IS the international language of choice.  Organizations like ISO
 or the UN treat English and French as equal, e.g. see here:

 <http://www.iso.org/iso/country_codes.htm>

 But, in actual reality, the lingua franca is English.  If you ask a Greek
 person what is the international name of their country, they’ll reply:
 Greece, not:  Grèce — unless you resurrect some educated person from the
 Thirties. :-D

 I imagine this would not be very different with people from other
 countries.

 Then, there are more practical problems:

 Aside from the fact that, since I’m not going to translate 500 city names,
 I will now be seeing the unhelpful message “500 untranslated and 10 fuzzy”
 — instead of “10 untranslated and 10 fuzzy” which helped me know where I
 was at...


 How is the sorting problem going to be solved?  Now translated strings sit
 at the same order their English original were.  That’s a problem.  But
 trying to solve it will cause other problems...

 My suggestion:

 Drop this file, or, at most, make a separate POT with the city names and
 then load localized city names (if they exist) with a new constant in wp-
 config.php.

 NOTE:

 What I’m saying does not come from indifference to the L10n issue.
 Localization of services and products is one of the things I care about
 the most, and I’m proud to have helped bring the Greek WP L10n to a
 completion state of about 99.5%, all in clear, plain language.  But I also
 try to be realistic and practical.

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