The security section of Mozilla seems to use the term "web site" and not "web site" as other places in mozilla. The use of the term "website" in one word or two words should be consistent.... http://lxr.mozilla.org/mozilla/search?string=website http://lxr.mozilla.org/mozilla/search?string=web+site

t->2.1 p3

Moving all P3 and P4 bugs targetted to 2.1 to future.

Mass assigning QA to ckritzer.

Mass reassign ssaux bugs to nobody

Mass change "Future" target milestone to "--" on bugs that now are assigned to nobody. Those targets reflected the prioritization of past PSM management. Many of these should be marked invalid or wontfix, I think.

I'll be happy to take this. Hopefully Thursday I can get the time to go through and fix these for the most part.

I'm putting this on here mainly to see if anyone will actually be interested in this. I agree that this is a polish issue... and that ONE FORM of "website" should be used through out the product. If you lookup "web site" at websters.com, the first entry is actually "website", so I assume that this is now the accepted nomenclature for one. Anyway, this is just a patch to assure that I'm on the right track. I won't patch any files affecting Firefox just yet. I'll gauge any interest they might have, via reaction to this bug. Assigning for review.

Comment on attachment 149249 [details] [diff] [review] Part one of the patches to hit all the necessary files. Requesting review from jag, since this is all basically string stuff. I realize that this isn't a complete patch. Just looking for an okay to continue with this. Thanks.

And also patched against an UP-TO-DATE trunk this time... hehe, whoops.

Comment on attachment 149253 [details] [diff] [review] Slightly larger, taking into account a couple more files. Changing review to new patch.

Comment on attachment 149253 [details] [diff] [review] Slightly larger, taking into account a couple more files. Looks good. sr=jag

Comment on attachment 149253 [details] [diff] [review] Slightly larger, taking into account a couple more files. I've checked this patch in.

(In reply to comment #7) > I won't patch any files affecting Firefox just yet. I'll gauge any interest > they might have, via reaction to this bug. Bloody devil, we're fragmenting over a non-app-specific term: http://www.mozilla.org/projects/help-viewer/documentation_language-style.php#terms Firefox uses "Web site" throughout (thus forcing Firefox Help to do likewise). Apparently Seamonkey now uses "website". What's worse is that "web site" has gained "substantial usage" (see link), but because it's still in the UI we're stuck there. There are a few little nits like this in UI and Help that are really annoying me. I'm sending R.J. Keller an email asking him to bring this and other issues up with Ben. This should be settled now to prevent imminent insanity.

I guess I'll hold off on the rest until I see if I need to do this the OTHER way around :(

Firefox 2.0b1 release candidate has a typo in the UI (the new phishing web site link needs renaming): Help-> "Report Broken Web Site..." Help-> "Report Phishing Website..." (should say Help-> "Report Phishing Web Site..." ) Also see BoxerBoi76's post which reported it here: http://forums.mozillazine.org/viewtopic.php?p=2364246#2364246

There are other examples of "web site" vs "website" inconsistency in Firefox bug 315987.

http://www.google.com/trends?q=web+site%2C+website Interesting to note that "website" outnumbers "web site" by a large margin, and that the preference for "web site" in news references is slowly losing ground. So, which is it going to be? :)

It's even worse, as "website" and "site" are equivalent in practically all our strings, see bug 385452

Filter "spam" on "guifeatures-nobody-20080610".

Serge, please refrain from assigning to default assignees for bugs that are currently assigned to nobody until bug 450902 is resolved. Default assignees/QAcontacts are still wrong for most SeaMonkey components.

http://mashable.com/2010/04/16/ap-stylebook-website/ http://twitter.com/APStylebook/status/12296505018

Given that bug 423282 addressed most of these cases in favor of "website" for en-US (it is my understanding that en-GB decided to use "web site" for their locale), along with a couple of follow-up bugs making similar changes, shouldn't this bug here closed or marked as a duplicate of 423282?

Yep, looks like we're done here - thanks :-)