Re: Bug#440938: ITP: xulrunner-l10n -- language packages for xulrunner
On Wed, Sep 05, 2007 at 05:11:51PM +0200, arno renevier <email@example.com> wrote:
> Package: wnpp
> Severity: wishlist
> Owner: arno renevier <firstname.lastname@example.org>
> * Package name : xulrunner-l10n
> Version : 1.8.1-1
> Upstream Author : Mozilla Project and Mozilla Localization Projects
> * URL : http://www.mozilla.org/projects/l10n/
> * License : GPL, LGPL, and MPL
> Description : language packages for xulrunner
> XULRunner is a single "gecko runtime" that can be used to bootstrap
> multiple XUL + XPCOM applications that are as rich as Firefox and
> This package provides localizations for xulrunner
> Additional informations:
> xulrunner-l10n will have similarity with iceweasel-l10n; some part of
> xulrunner-l10n source will come from iceweasel-l10n source package, other part
> will come from mozilla cvs.
> source package will provide 43 localization packages + one meta package
> xulrunner-l10n-all which depends on all localization packages.
> Unlike iceweasel-l10n, localization packages will not be installed as
> extensions, but directly in /usr/share/xulrunner/chrome because current version
> of xulrunner does not allow global extensions for all applications. Hopefully,
> that will change in the future, and localization packages could be real mozilla
Actually, it *does* allow global extensions, but applications embedding
libxul or using xulrunner have to initialize the extensions manager by
themselves in order to get these extensions enabled. This is something that
is, unfortunately, not very likely to change.
Note having added stuff in the chrome without extensions recently, I can't
tell you if it will be necessary to go through a registration phase, but
I think putting a chrome.manifest file alongside should be enough.
If it is not, please bug me so that we find something (which might be in
the form of a script provided by the libxul package)