Talk:Specification of Language Pack UI for Applications and Extensions

From MozillaWiki
Revision as of 13:27, 31 January 2006 by AxelHecht (talk | contribs) (Commenting on the extension langpacks from an l10n pov.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Comments by l10n@

I don't see any reason to restrict ourselves to one language pack.

The UI should just list the available locales for that extension and be done for it. Or rather, how about it showing only those locale packs that don't match the current general.useragent.locale?

So extension foo with german, french and en-US locales would be listed to a german user as "Meine Erweiterung (en-US, de, fr)"

The extension should show it's available locales in general if none of the available ones match the currently selected ones.

Such as "Another Extension (en-US)".

I don't think that we need to expose any language selection for extensions, this should just fall back to the fuzzy locale selection that the chrome registry already has.

Regarding update, updates to an installed locale pack only should be possible, I don't see that being layed out clearly.

Regarding installing a langpack for a non-existing extension, we should just require langpacks to require their extension, we will have extension deps for 2.0, right?

One point that wasn't mentioned yet is conflicting langpacks. Two different localizers localize the same extension, and a user wants to switch over. Though that sounds like something we could postpone to 3.0.

--AxelHecht 05:27, 31 Jan 2006 (PST)