Closed Bug 742331 Opened 12 years ago Closed 12 years ago

[nn-NO] Translate updated home page for 3.x users

Categories

(Websites :: Other, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: pascalc, Assigned: mail)

References

Details

On April 24, Firefox 3.6 will reach it's end of life and will no longer be supported.

The Firefox start page is currently google.com/firefox (hosted by Google), when 3.6 is no longer supported, that page will no longer be proposed and Firefox users of older unsupported versions of Firefox will see a page hosted on mozilla infrastructure instead of Google with the same functionnality but with a big warning about their version being obsolete.

We need to translate a few strings for this warning as well as translate the strings that were in the search page interface provided by Google

Here is the staging server:
http://start-dev.allizom.org/nn-no

(The file already has a couple of strings translated from mozilla.org)

The file is stored in a separate repository, here is the url to the reposirory:
http://svn.mozilla.org/projects/l10n-misc/trunk/fx36start/locale/nn-NO/

and a direct link to the file:
http://svn.mozilla.org/projects/l10n-misc/trunk/fx36start/locale/nn-NO/fx36start.lang

Please send your translation to the above repo or alternatively attach it to this bug and I will commit for you.

Don't forget to save your file as utf8 as usual :)

Thanks!
Assigning to Håvard.
Håvard, I know this is nn-NO and not nb-NO but do you think you could do this one or find some volunteer to do it? 

Otherwise, I propose to display the page in Bokmål instead of Nynorsk.

Thanks
Assignee: nobody → havard.mork
r104323

I personally would not mind if all nn-NO web pages on mozilla.com were redirected to nb-NO. I don't want to make that decision, since there are other contributors involved, but the effort would surely be more useful in product l10n, and product testing, for such a small locale.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.