Comment #9 on issue 21080 by [email protected]: chromium doesn't honor  
locale fallbacks
http://code.google.com/p/chromium/issues/detail?id=21080

The following revision refers to this bug:
     http://src.chromium.org/viewvc/chrome?view=rev&revision=27608

------------------------------------------------------------------------
r27608 | [email protected] | 2009-09-30 07:26:59 -0700 (Wed, 30 Sep 2009)  
| 11 lines
Changed paths:
    M  
http://src.chromium.org/viewvc/chrome/trunk/src/app/l10n_util.cc?r1=27608&r2=27607
    M  
http://src.chromium.org/viewvc/chrome/trunk/src/app/l10n_util_unittest.cc?r1=27608&r2=27607

[Linux] Supports the LANGUAGE environment variable.

This CL adds the support for the LANGUAGE environment variable, which is  
supported by gettext based applications for specifying a priority list of  
user prefered locales for UI messages translation.

Unlike gettext based applications, which support using different locales  
for messages translation and other locale categories, like LC_CTYPE,  
LC_COLLATE, LC_TIME, etc., chromium supports only one application locale  
for all localization operations.
This CL adds the support of specifying the application locale by LANGUAGE  
env variable, but doesn't make chromium to support above mentioned behavior  
of gettext based applications.

BUG=21080: chromium doesn't honor locale fallbacks
TEST=Launch chrome with LANGUAGE=br:fr_FR:fr, French locale shall be used  
by chrome, as br is not supported by chrome yet.

Review URL: http://codereview.chromium.org/236001
------------------------------------------------------------------------


--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to