On Tue, Nov 10, 2009 at 3:24 PM, Nebojša Ćirić <c...@google.com> wrote:
>> Implementation notes:
>>
>> In order to avoid slowing down Chrome startup, I think we need to
>> store the manifest in the preferences already localized. So basically,
>> somewhere during extension installation, we need to localize the
>> manifest and store it that way. Whenever the current locale in Chrome
>> changes, we must re-localize from the version stored on disk.
>
> We could generate all manifest.json files during the installation process
> and store them in respective locales:
> _locales/en/manifest.json
> _locales/es/manifest.json
> When user switches UI language, we would load correct manifest.json file and
> replace one in prefs.
> I think this would be cheaper (perf wise) than loading message catalogs when
> we detect UI language change, and then doing manifest localization on the
> fly (less files to load, less processing).
I think it is OK to re-read the catalogs when the UI language changes.
This is pretty infrequent.
- a
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
