diff options
| author | jshin@chromium.org <jshin@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-10-30 00:18:22 +0000 |
|---|---|---|
| committer | jshin@chromium.org <jshin@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-10-30 00:18:22 +0000 |
| commit | c16605de2a5f9fc7c16cb6c185e565e503667165 (patch) | |
| tree | 34045b1a4fc73a7fa8329c49d45bd158b8d78fcd /testing | |
| parent | 405acd1cd89d050b17c965ffa8dba6b8c93966cb (diff) | |
| download | chromium_src-c16605de2a5f9fc7c16cb6c185e565e503667165.zip chromium_src-c16605de2a5f9fc7c16cb6c185e565e503667165.tar.gz chromium_src-c16605de2a5f9fc7c16cb6c185e565e503667165.tar.bz2 | |
Use GLib to parse environment variables to determine the default locale.
Switch to using GLib, instead of having a Chromium specific implementation, for
parsing environment variables for language preferences for all POSIX systems
that use GTK+. If we have a non-GTK port in the future, we have to resurrect
our custom code.
This will guarantee that UI language selection in Chromium works just like for
all other GTK+ applications, and simplify the code.
While doing this, also do some cleaning-up of the language preferences code and
add a test case to verify that the prioritization is done correctly.
Original CL by Fredrik Roubert at http://codereview.chromium.org/2901004/show
BUG=NONE
TEST=app_unittest with "--gtest_filter=L10nUt*.*Loc*" passes.
Review URL: http://codereview.chromium.org/4217004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64524 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'testing')
0 files changed, 0 insertions, 0 deletions