Closed Bug 419614 Opened 12 years ago Closed 12 years ago
missing multi language feature in lightning
the lightning.xpi contains only en_US, but the build should be multi lingual. See chrome.manifest: locale calendar en-US jar:chrome/calendar-en-US.jar!/locale/en-US/calendar/ content calendar jar:chrome/calendar.jar!/content/calendar/ skin calendar classic/1.0 jar:chrome/calendar.jar!/skin/classic/calendar/ locale lightning en-US jar:chrome/lightning-en-US.jar!/locale/en-US/lightning/ overlay
the according Makefile checks for existing localisations in a l10n directory beside the mozilla tree. by default there isn't one on the non-l10n tinderboxes. to get multi-language lightning.xpi there are two options (with different pros and cons): - modify the l10n tinderbox to supply multi-language lightning too - run lightning tinderboxes with MOZ_CO_LOCALES set
Ause, what are the different pros and cons?
here's my, probably incomplete, list first solution (l10n tb): - pro: no additional l10n tree (means diskspace, checkout) - con: two lightning.xpi. one en-US only, the other localized - con: unknown amount of tweaking to get a non-building tb to create a lightning.xpi second solution (extra l10n tree): - con: additional l10n tree - con: unknow sideeffects when setting MOZ_CO_LOCALES - pro: no further implementation required
reading the list again, i tend to the second option ;)
I don't know who and how he is making it, but the release versions were always multi-lingual... Is it really needed to get a multi-language nigthly? It would still be possible by manually changing the locales AFTER the build - but is it's worth the trouble?
Ause, Andreas: Why should this bug block 0.8? Are we currently unable to create multilang-XPIs?
as you can see, there aren't any, except for the two boxes that still build to experimental tree where i already activated option two.
I checked this with the latest nightly builds 2008030502. The multilanguages feature is available now -> set this issue to WFM.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Flags: blocking-calendar0.8? → blocking-calendar0.8-
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.