On Thu, Nov 26, 2009 at 3:55 PM, Jeremy Selier <jerem.sel...@gmail.com> wrote: > Anyone? From my tests it seems like the order is like the order of > Accept-Language header of HTTP : > http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.4 I just > want to be sure I can base my detection on this.
I would assume this is right, but Cira will know for sure. > Also, am I right to code everything from the ground to deal with i18n, > like building a JavaScript array of all my translations and load them > based on the result of chrome.i18n.getAcceptLanguages or will this > design document > http://sites.google.com/a/chromium.org/dev/developers/design-documents/extensions/i18n > be up and running for the launch of extensions? For beta, we will not have anything more than what we have now. So if you need i18n for beta, you'll have to make do with what's there. For stable, we intend to have what we have now, plus i18n of the manifest text strings. We may also have substitution of strings in HTML, but that isn't clear yet. - a -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensi...@googlegroups.com. To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
