On Tue, Nov 10, 2009 at 2:31 PM, Erik Kay <[email protected]> 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 got is a good start for our initial release. The above > omissions are going to be trickier to do without significant performance > penalties, and I think we can add them later. This will mean that i18n will > be more manual for developers with the initial release, but it should still > perform well and should be forwards compatible. > 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 when > we do implement localized resource fetching.
One thing is that odd is that if we don't do fallback for getURL(), it will be inconsistent. The manifest and getMessage() API will localize using fallback, but getURL() won't. - a -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=.
