Package: wnpp
Severity: wishlist

* Package name    : mozilla-firefox-locale-sv
Version         : 0.9.3
Upstream Author : Mikael Hedberg <hedberg@novasphere.net>
* URL             : http://www.mozilla.se/firefox.shtml
* License         : MPA
Description     : Mozilla Firefox Swedish Language/Region Package

Swedish Menu/Message resource and Region property package for Mozilla Firefo
x.


-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.8.1
Locale: LANG=sv_SE.iso-8859-1, LC_CTYPE=sv_SE.iso-8859-1 (ignored: LC_ALL se
t to sv_SE)


--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.or
g

[ Post a follow-up to this message ]

* Sep 26 12:22 Josselin Mouette <joss@debian.org>:
> Le vendredi 17 septembre 2004 à 19:20 +0200, Johan Svedberg a écrit : 
>
> Nothing against this specific package, but am I the only one to find
> all these mozilla-*-locale-* source packages are a huge waste of human
> resources and a complete mess for our users? Specific language
> packages for big hogs like KDE or OOo make sense, but we have already
> 42 separate *source* packages for mozilla l10n stuff, all having to be
> upgraded simultaneously with every new mozilla version.
>
> 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.

Again, sorry about the multiple ITP:s. How come relaying on master is
laggning so much?

-- 
Johan Svedberg, johan@svedberg.pp.se, http://johan.svedberg.pp.se/

[ Post a follow-up to this message ]

On Sun, Sep 26, 2004 at 01:44:09PM +0200, Johan Svedberg wrote:
> * Sep 26 12:22 Josselin Mouette <joss@debian.org>: 
> 
> I agree. It would be great if something like that could be co-ordinated.
> 
> Again, sorry about the multiple ITP:s. How come relaying on master is
> laggning so much?


Perhaps opening a project on Alioth with a mailing list, and then
"calling" other maintainers is a first step... pity that Alioth is a
bit "unreliable" right now

Cheers,

-- 
Jose Carlos Garcia Sogo
jsogo@debian.org

[ Post a follow-up to this message ]

On Sun, Sep 26, 2004 at 01:44:09PM +0200, Johan Svedberg wrote: 
> 
> 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 &
#91;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....illa/l10n/lang/
[3] 
[url]http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/XXX/contrib-localized/[/ur
l]     
[4]http://ftp.mozilla.org/pub/mozilla.org/thunderbird/releases/XXXXX/con
trib-localized/

[ Post a follow-up to this message ]

On Mon, Sep 27, 2004 at 06:42:23PM +0200, Javier Fernández-Sanguino Peña wrote:
> 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 devis
e
> its own (as well as redoing the registration of the packages in mozilla as
> documented at [1])

For that you need no more than call update-mozilla*-chrome scripts.

Mike


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.or
g

[ Post a follow-up to this message ]