676159 - Please create MU billboard for Sea2.3 as "unsupported" scary warning

Status: RESOLVED FIXED

(SeaMonkey :: Release Engineering, defect)

Description

[Justin Wood (:Callek)]

See for reference:
http://www.mozilla.com/en-US/firefox/unsupported/details/

If you merely do a s/Firefox/SeaMonkey/ (besides style stuff) I can probably use the l10n that Firefox has already. But I'll leave the en-US page up to you.

Comment 1

[Justin Wood (:Callek)]

Jens, did this drop through your inbox?

Comment 2

[Jens Hatlak (:InvisibleSmiley)]

Attachment: billboard ZIP

(In reply to Justin Wood (:Callek) from comment #1)
> Jens, did this drop through your inbox?

Yeah, got marked read somehow.

The attached only contains the new/updated files. Unlike FF, I didn't do it using some "unsupported" path but per version. As per your request I kept the strings FF is using (with s/FF/SM/), except for the page title where I found our existing string was better (YMMV).

Comment 3

[Justin Wood (:Callek)]

(In reply to Jens Hatlak (:InvisibleSmiley) from comment #2)
> The attached only contains the new/updated files. Unlike FF, I didn't do it
> using some "unsupported" path but per version. As per your request I kept
> the strings FF is using (with s/FF/SM/), except for the page title where I
> found our existing string was better (YMMV).

Ok, pushed to unsupported though, I prefer it there, so we don't have to refresh this every time (just have to refresh the url of the update binary).

I kept the en-US <title>...</title> intact, but on the translation pages, I basically used the Firefox version, that difference is not as big a deal imo.

Also pushed pages for all locales, copied from the locale translations for Firefox, I have slight concerns over gender/case/etc. of SeaMonkey as opposed to Firefox, so I will still get l10n bugs on file to have those teams track this.