Closed Bug 537481 Opened 10 years ago Closed 10 years ago
Don't ship dictionaries with language packs
SeaMonkey currently ship dictionaries with language packs but unfortunately, the licensing story there is somewhat unclear and it's probably not optimal to lose a selected dictionary when switching locales, so it's best to follow what Firefox and Thunderbird are doing and just exclude dictionaries from SeaMonkey builds.
This should be it. I don't have a locale around that builds and/or has a dictionary right now, so I can't test it atm, but normal build is not broken and this should be trivial. Axel, there's nothing else where we should refer to this, right?
Attachment #419767 - Flags: review?(l10n)
Comment on attachment 419767 [details] [diff] [review] don't include dictionaries in langpacks The clobber-zip piece should stay, otherwise you're breaking the dictionaries for the binary builds. I guess the trailing ';' can go, too. Compare with the target in l10n.mk, http://mxr.mozilla.org/mozilla-central/source/toolkit/locales/l10n.mk#175 The only difference should be the searchplugins there.
Attachment #419767 - Flags: review?(l10n) → review-
Thanks for looking at this, Axel. I actually think our searchplugins don't even work from an extension, so it's probably better to not package them as well and only have stuff in there that actually works (i.e. chrome only). With that, the new patch should fully sync our langpacks to those Firefox ships (and make conversion to l10n.mk easier in the future).
Comment on attachment 419781 [details] [diff] [review] v2 - fully sync with what Firefox does Sounds good.
Attachment #419781 - Flags: review?(l10n) → review+
Pushed on trunk as http://hg.mozilla.org/comm-central/rev/d8bdb40b098a
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.1a1
Attachment #419781 - Flags: approval-seamonkey2.0.3? → approval-seamonkey2.0.3+
Pushed on branch as http://hg.mozilla.org/releases/comm-1.9.1/rev/eeb567bb0464
You need to log in before you can comment on or make changes to this bug.