On Tue, Nov 10, 2009 at 2:31 PM, Erik Kay erik...@google.com wrote:
To be clear what's (intentionally) omitted from this proposal:
- localized resource fetching (transparently turning /foo/bar.gif into
/_locales/jp/foo/bar.gif)
- auto string substitution (l18n templating)
I think what you've
On Tue, Nov 10, 2009 at 3:21 PM, Nebojša Ćirić c...@google.com wrote:
One minor thing you left out was getURL providing a way to generate a
localized URL (ideally without stats). If we don't provide devs a way
to
construct URLs manually, then they won't have a good migration path for
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
On Tue, Nov 10, 2009 at 3:31 PM, Aaron Boodman a...@chromium.org wrote:
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
