504054 - Make Swedish localization ready for SeaMonkey 2 release

Status: RESOLVED FIXED

(Mozilla Localizations :: sv-SE / Swedish, enhancement)

Description

[Lars P M]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; sv-SE; rv:1.8.1.21) Gecko/20090303 SeaMonkey/1.1.15 (Ubuntu-1.1.15+nobinonly-0ubuntu2) reconfigured by user.js v1.1
Build Identifier:  

The Swedish localization of SeaMonkey 2 has not been updated for some time and I'm not opting it in for the beta 1 release. It should be considered as a bug (enhancement bug) if there would be no beta (not even beta 2 or 3) in Swedish. Me myself will probably not have the time to work on it before September, so this bug report is a reminder of that state, and also the opportunity for someone else to step in (even though I'm not planning to completely opt out so to speak ;-)

Reproducible: Always

Actual Results:  
There is only an (early) alpha of SeaMonkey 2 in Swedish.

Expected Results:  
There should be a beta of SeaMonkey 2 in Swedish.

Comment 1

[Peter Kihlstedt :peki]

I have offered Lars help in translating SeaMonkey 2 into Swedish. But I am not familiar with the translation process here so I need some guidance to get going.

Regards
Peter

Comment 2

[Stefan [:stefanh]]

I guess https://wiki.mozilla.org/SeaMonkey:Localization is a good starting point for some general information. Not really sure what you mean with the translation process, though. Note that the SeaMonkey sv-SE source already is in a mercurial repository, can be seen at http://mxr.mozilla.org/l10n-mozilla1.9.1/source/sv-SE/suite (the 'suite' directory is the seamonkey-specific parts). So, the source is there. I'm not too familiar with the workflow and I think you should ask Lars about it, but the result of the workflow is that you push your changes to the central repository. Lars doesn't have access to the repository (you need special permits and you have to apply for it), but Hasse might be able to push the changes for you. I think it's probably better to sort these things out in a newsgroups or by private e-mail, though.

There's also a l10n dashboard at http://l10n.mozilla.org/dashboard/ (sea2.0 is the seamonkey part) where you can see various information about the l10n status for each locale/product.

Comment 3

[Stefan [:stefanh]]

Btw, Lars: I take it that you're not going to be able to make it yourself for 2.0 final?

Comment 4

[Lars P M]

(In reply to comment #3)
> Btw, Lars: I take it that you're not going to be able to make it yourself for
> 2.0 final?

True. Peter wrote me an e-mail a week ago, so I welcomed his interest to go on with SM 2, and directed him towards this bug. I simply have too much with my daytime job, to be of any use at this moment in time. Hopefully you, Stefan, and Hasse might be ready to assist, so we keep the pace up :-)

Comment 5

[Stefan [:stefanh]]

Peter, for mercurial info, see https://developer.mozilla.org/en/L10n_on_Mercurial

Comment 6

[Stefan [:stefanh]]

Dashboard is green :-) Looks like Peter have done a great job! I'm morphing the description of this bug to better reflect reality. Also putting the chatzilla bug to block this one, so it can be tracked.

Comment 7

[Stefan [:stefanh]]

This is obviously fixed :-)