On Sun, Sep 26, 2004 at 01:44:09PM +0200, Johan Svedberg wrote: > > If mozilla's upstream is not able to deal with i18n at all, maybe we > > could start a central mozilla-locale project, at least to group all > > these sources in a single package for which upgrades would be easier. > > I agree. It would be great if something like that could be co-ordinated. I agree too. Actually, it makes more sense if we do a single package and integrate there mechanisms to extract the needed files from xpis to generate mozilla-locale-* packages instead of having each maintainer devise its own (as well as redoing the registration of the packages in mozilla as documented at [1]) Moreover, somebody (a packaging group) could just package the locale definitions available for Mozilla [2], Firefox [3] and Thunderbird [3], update them from time to time and update them whenever a new release is produced. That would avoid all the bugs related to XXXX-locale-YYY packages not allowing transitions of new Mozilla|Firefox|Thunderbird versions because they have not been updated and having the binary package proceed into testing would break them. I believe that's actually how Mozilla is integrated in other OS, for example, in Solaris IIRC. Regards Javier [1] http://www.mozilla.org/projects/l10n/mlp_distrib.html [2] http://ftp.mozilla.org/pub/mozilla.org/mozilla/l10n/lang/ [3] http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/XXX/contrib-localized/ [4]http://ftp.mozilla.org/pub/mozilla.org/thunderbird/releases/XXXXX/contrib-localized/
Attachment:
signature.asc
Description: Digital signature