Updates:
Cc: [email protected]
Comment #14 on issue 26856 by [email protected]: Today's date is not
internationalized in chrome history
http://code.google.com/p/chromium/issues/detail?id=26856
Hmm.. I don't think setting the ICU default locale is blocked by sandbox.
Moreover,
domUI date formatting is done in the browser process, I believe. (I might
be wrong. '-
-no-sandbox' flag doesn't do anything, does it? )
When I set the ICU locale to a hard-coded value (e.g. "ja") instead of
what I get from
NSLocale in GetApplicationLocale() in l10n_util_mac.mm, date is formatted in
Japanese.
So, back to my question: Why does NSLocale return 'en-US'? Is it blocked by
the
sandbox? If domUI date formatting is done in the browser process, it
shouldn't
matter...
Anyway, each renderer process (and plugin / utility process) has to inherit
the UI
locale from the browser process and the ICU default locale is set
accordingly (webkit
passes an explicit locale param when calling ICU apis, but there are other
cases that
do not). So, I agree with you on what you wrote in comment #12.
--
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