The string "seperator" appears many times in the source, including variable names, etc. The correct spelling is "separator." http://lxr.mozilla.org/seamonkey/search?string=seperator

alecf: http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/xpfe/global/resources/content/nsTreeController.js&rev=1.8&mark=129,48#125 http://lxr.mozilla.org/mozilla/search?string=seperatorUri your code is broken. hrm, i guess that means we need to make sure that we weren't padding around it.

There are also some occurrences of other forms like "seperate" and "seperating," mostly in comments http://lxr.mozilla.org/seamonkey/search?string=seperat

For the change below. I don't see any matching definition of this value, in the patch, which leads me to believe something was missed. But a lxr search only turns up this, so I think something else is wrong here. =================================================================== RCS file: /cvsroot/mozilla/xpfe/global/resources/content/nsTreeController.js,v retrieving revision 1.8 diff -u -0 -r1.8 nsTreeController.js --- xpfe/global/resources/content/nsTreeController.js 2001/09/28 20:14:05 1.8 +++ xpfe/global/resources/content/nsTreeController.js 2001/10/24 14:44:31 @@ -129 +129 @@ - if (type == seperatorUri) + if (type == separatorUri)

Found some stuff about common spelling mistakes: http://www.internetqa.com/web_tests/spelling/articles.htm http://www.ricksoft.com/spello.htm

More spelling fun: http://lxr.mozilla.org/seamonkey/search?string=persistant http://lxr.mozilla.org/seamonkey/search?string=persistance http://lxr.mozilla.org/seamonkey/search?string=priviledge http://lxr.mozilla.org/seamonkey/search?string=protocal http://lxr.mozilla.org/seamonkey/search?string=editting http://lxr.mozilla.org/seamonkey/search?string=editted http://lxr.mozilla.org/seamonkey/search?string=targetted http://lxr.mozilla.org/seamonkey/search?string=targetting http://lxr.mozilla.org/seamonkey/search?string=useable http://lxr.mozilla.org/seamonkey/search?string=noticable http://lxr.mozilla.org/seamonkey/search?string=managable http://lxr.mozilla.org/seamonkey/search?string=usefull http://lxr.mozilla.org/seamonkey/search?string=dependant http://lxr.mozilla.org/seamonkey/search?string=primative http://lxr.mozilla.org/seamonkey/search?string=existance

The first use of separatorUri doesn't show up in the patch because it uses the correct spelling: http://lxr.mozilla.org/seamonkey/source/xpfe/global/resources/content/nsTreeController.js#48

boehm requires mail to the maintainer (not a mozilla.org project) glib requires mail to someone (gnome.org) re dbradley's concern yes, it took me a bit, but you'll note that my bonsai url included the other spelling. patches for the other stuff coming. some minor conerns: NSPR and PSM are locked, there is code in both to be changed, i'll try to separate those out.

One more: http://lxr.mozilla.org/seamonkey/search?string=broser (browser?)

Ok, good, then this actually fixes a bug as well as clean up this mispelling.

Comment on attachment 54865 [details] [diff] [review] s///g by perl r=dbradley I built with the patch under Linux and Win32. No problems.

/xpinstall/wizard/windows/setup/extra.c, line 6068 -- /* check for both 'Verify Existance' and 'Verify Existence' */ It appears there's going to be one place where i don't get to do the change :-o filed bug 106832, bug 106839, bug 106836, and bug 106842 for some code changes. I'll file a bug for peristant* code changes too.

the most important: http://lxr.mozilla.org/mozilla/search?string=mozila

more of that: http://lxr.mozilla.org/mozilla/search?string=nestcape http://lxr.mozilla.org/mozilla/search?string=expresion http://lxr.mozilla.org/mozilla/search?string=eveluate http://lxr.mozilla.org/mozilla/search?string=charcaters http://lxr.mozilla.org/mozilla/search?string=sorce+socket http://lxr.mozilla.org/mozilla/search?string=retunr http://lxr.mozilla.org/mozilla/search?string=adress http://lxr.mozilla.org/mozilla/search?string=sesion http://lxr.mozilla.org/mozilla/search?string=hmtl http://lxr.mozilla.org/mozilla/search?string=acess http://lxr.mozilla.org/mozilla/search?string=suport http://lxr.mozilla.org/mozilla/search?string=mesage http://lxr.mozilla.org/mozilla/search?string=controler http://lxr.mozilla.org/mozilla/search?string=comand http://lxr.mozilla.org/mozilla/search?string=atribute http://lxr.mozilla.org/mozilla/search?string=fucntion http://lxr.mozilla.org/mozilla/search?string=warnning

Another http://lxr.mozilla.org/mozilla/search?string=delimeter ("delimiter") You can probably chase spelling errors in the source all day and still never fix them all--maybe just find and fix the most important ones? That of course begs the question of which ones are important....

Submitted two patch files. First is for safe spelling corrections within comment blocks for these cases: http://lxr.mozilla.org/mozilla/search?string=nestcape http://lxr.mozilla.org/mozilla/search?string=expresion http://lxr.mozilla.org/mozilla/search?string=eveluate http://lxr.mozilla.org/mozilla/search?string=charcaters http://lxr.mozilla.org/mozilla/search?string=sorce+socket http://lxr.mozilla.org/mozilla/search?string=retunr http://lxr.mozilla.org/mozilla/search?string=adress http://lxr.mozilla.org/mozilla/search?string=sesion http://lxr.mozilla.org/mozilla/search?string=hmtl http://lxr.mozilla.org/mozilla/search?string=acess http://lxr.mozilla.org/mozilla/search?string=suport http://lxr.mozilla.org/mozilla/search?string=mesage http://lxr.mozilla.org/mozilla/search?string=controler http://lxr.mozilla.org/mozilla/search?string=comand http://lxr.mozilla.org/mozilla/search?string=fucntion http://lxr.mozilla.org/mozilla/search?string=warnning Second is for corrections to misspellings in identifiers; I haven't tested compilation even, so merge and let me know if you need any tweaks: http://lxr.mozilla.org/mozilla/search?string=atribute http://lxr.mozilla.org/mozilla/search?string=delimeter http://lxr.mozilla.org/mozilla/search?string=depricated NOTES: depricated, delimeter, atribute: Test well since these are misspelled in identifiers. acess: Not corrected: /l10n/tools/mozxlator/gui/dialog/EditPhraseDialog.java, line 78 ... Comments state not to edit this code; it's generated by a GUI builder of some type. adress: Not corrected: /mstone/doc/MailStone.html, line 1409 -- be inserted into the first <FONT FACE="courier, courier new, monospace">%ld</FONT> in the <FONT FACE="courier, courier new, monospace">adressFormat</FONT>. /mstone/doc/stone.mif, line 15908 -- <OKWord `adressFormat'> /mstone/doc/stone.mif, line 16851 -- <String `adressFormat'> Also not corrected were German correct spellings of adresse (mainly in the I10N locale files). sesion: Please inspect: http://lxr.mozilla.org/mozilla/source/xpfe/components/autocomplete/src/nsLDAPAutoCompleteSession.cpp#154 suport: Please inspect: http://lxr.mozilla.org/mozilla/source/editor/libeditor/html/nsHTMLEditRules.cpp#4509 And #4510 as well (seems good to me) Not changed: /security/jss/org/mozilla/jss/pkix/cmc/OtherInfo.java, line 56 -- public static final int UNSUPORTED_EXT = 5; Couldn't see that any other Java code (maybe external?) depended on it. mozila: These need to be looked at: http://lxr.mozilla.org/mozilla/search?string=mozila I do have the shell/sed scripts I cobbled together for search/replace.

Ho hum http://lxr.mozilla.org/seamonkey/search?string=referer http://lxr.mozilla.org/seamonkey/search?string=refering

Comment on attachment 55962 [details] [diff] [review] Correct misspellings within comment blocks (safe changes) r=adamlock

he, he, he...: http://lxr.mozilla.org/mozilla/search?string=mispelled

/gfx/src/xprint/xprintutil_printtofile.c, line 379 -- /* remove the file if not successfull */

http://www.howto4u.com/testimonials.htm has a nice list, i'll need to see if any of them apply here. i think if alright appears in mozilla i'll leave it alone, as m-w says it's ok.

http://lxr.mozilla.org/mozilla/search?string=indepenant s!ile!file! /xpfe/global/resources/content/bindings/general.xml, line 50 -- - outliner's so we can build in some of the ile behavior (such as going s!build indepenant!built independently! /modules/zlib/src/makefile.win, line 27 -- # New build system where zip dll is build indepenant of java stubs. /mailnews/mime/cthandlers/calendar/makefile.win, line 38 -- # New build system where zip dll is build indepenant of java stubs. /mailnews/mime/cthandlers/glue/makefile.win, line 31 -- # New build system where zip dll is build indepenant of java stubs. /mailnews/mime/cthandlers/smimestub/Makefile.win, line 31 -- # New build system where zip dll is build indepenant of java stubs. /mailnews/mime/cthandlers/vcard/makefile.win, line 40 -- # New build system where zip dll is build indepenant of java stubs. s!build!built! /netwerk/build/nsNetModule.cpp, line 683 -- // The register functions for the build in

http://lxr.mozilla.org/mozilla/search?string=wanto

I'm surprised nobody has mentioned this before: http://lxr.mozilla.org/seamonkey/search?string=propogat q.v. http://bugzilla.mozilla.org/show_bug.cgi?id=62971#c17 and http://bugzilla.mozilla.org/show_bug.cgi?id=108736

note: ILE isn't actually a misspelling. :-(

Comment on attachment 62238 [details] [diff] [review] Next round: Comment 23 .. Comment 29 r=cmanske

Comment on attachment 62238 [details] [diff] [review] Next round: Comment 23 .. Comment 29 sr=jst

this was done by loading all files into wordperfect. it took quite a while.

wtc: could you please exmanine and land the nspr changes? the only one which i didn't do consistently was indemnify which is consistently misspelled in a legal block. mitchell: should i be correcting that misspelling (if so i guess wtc would have to fix the instance i missed)

http://lxr.mozilla.org/seamonkey/search?string=off-line should be "offline" http://lxr.mozilla.org/seamonkey/search?string=on-line should be "online"

bookmakrs

peterl contributed 'realtive'

mitchell, someone introduced a bade meme into license headers, http://lxr.mozilla.org/mozilla/search?string=oqr Do i need special permission to fix it?

Go ahead and fix it. The published version of the MPL doesn't even have this typo in it, so there's no issue. mitchell

s/bade/bad/ *sigh* ok, i'll try to have my next patch by sunday night.

ie. => i.e., eg. => e.g.

http://lxr.mozilla.org/seamonkey/search?string=comonents http://lxr.mozilla.org/seamonkey/search?string=failes http://lxr.mozilla.org/seamonkey/search?string=prefered http://lxr.mozilla.org/seamonkey/search?string=recursivly http://lxr.mozilla.org/seamonkey/search?string=somwhere

Oops, forgot one: http://lxr.mozilla.org/seamonkey/search?string=comparision

I'm glad to see I'm not the only one who makes this mistake: http://lxr.mozilla.org/seamonkey/search?string=similiar

Comment on attachment 74694 [details] [diff] [review] Next round: Comment 37 .. Comment 46 sr=blake

Comment on attachment 74694 [details] [diff] [review] Next round: Comment 37 .. Comment 46 r=db48x

Comment on attachment 74694 [details] [diff] [review] Next round: Comment 37 .. Comment 46 i won't check in the changes to other-licenses. i'll try to find some people to contact about them. wtc: can you arrange to commit/review the nss changes?

Comment on attachment 74694 [details] [diff] [review] Next round: Comment 37 .. Comment 46 a=asa (on behalf of drivers) for checkin to the 1.0 trunk

*** Bug 133028 has been marked as a duplicate of this bug. ***

from bug 133028: The XPCOM api uses flavor everywhere. The JS helper functions in nsDragAndDrop etc. all use flavour. This is driving me crazy. Can we change to the consistent use of the American spelling (Best before the 1.0 Release and widespread usage). Only the JS code need be changed.

Where does it say that Mozilla is an American project? Flavour is the correct spelling in most English speaking counties other than America. Please don't change this. This whole bug is honestly a waste of time and bandwidth as it forces people to pull down all these changes and rebuild with them, with the changes providing little if any benefit. Don't you have better things to do with your time?

That bug asks for consistency. Which is a very reasonable request. However I'm not going to make any fix for that bug under this bug's banner.

has the 03/17/02 patch landed? if so can you please mark it obsolete so this doesn't look like an approved change ready to land? thanks.

Should bug 93834 block this one?

perhaps also: http://lxr.mozilla.org/seamonkey/search?string=fuck he, he, he...:)

Actually, ignore my last comment. It turns out that is a (correct) alternate spelling.

*** Bug 195594 has been marked as a duplicate of this bug. ***

Fixes avilable, equivilent, equivilant, juast, and a few others.

Fixed patch

Final Patch

Comment on attachment 117682 [details] [diff] [review] Spelling Patch - Final Version sr=dmose

Comment on attachment 117682 [details] [diff] [review] Spelling Patch - Final Version r=doron

How can this "Final Version" be considered reviewed/super-reviewed when it doesn't fix the problems noted in some of the other patches? widget/src/xpwidgets/nsTransferable.cpp still contains "Avilable", but was obsoleted by this patch. There are probably others as well.

Im sorry for the confusion. That was not a "Final Patch", It was just the final version of that patch. I attached 3 versions of that patch I believe, so I just called that one the final version for clarity. I'll fix the avilable in my next patch, tomorrow most likely.

Reassiging to me, and cc'ing timeless by request. I'll have that instance of avilable fixed soon. I thought I caught all of them except the ones in security/nss and NSPR which are locked.

Comment on attachment 117682 [details] [diff] [review] Spelling Patch - Final Version Obsoleting since it is checked in now

This patch fixes most occurences of seper*

Comment on attachment 118230 [details] [diff] [review] Fixes for seper* + if (printData.mPrintFramesSeparatly) "mPrintFramesSeparately" please +ePrintFramesSeparatlyControlID, here too +resource 'CNTL' (ePrintFramesSeparatlyControlID, "Print Frames Separately", purgeable) { and here + ControlRef thePrintFramesSeparatly; again field, we must make it be a well-formed continuation line, - by seperating the old and new data with CR-LF-TAB. + by separating the old and new data with CR-LF-TAB. indentation is wrong here is one) or `group' (if there is one) or `host_and_port' (otherwise.) - Seperate the search data from what it is clinging to, being careful + Separate the search data from what it is clinging to, being careful here too +/* * - fixed separate read() & display() processing * */ libmng is an external library... please tell gjuyn@3-t.com about your changes. - // Since the Mac doesn't consider each window a seperate process this call functions + // Since the Mac doesn't consider each window a separate process this call functions // slightly different than on other platforms. We first check to see if we're the wrong indentation - functions; working similar to the above. (they have the semantic + functions; working similar to the above. (they have the semantic again. and what is the change here, anyway? - functions that will return a newly allocated string seperatedly. all of + functions that will return a newly allocated string separately. all of again - # Compile a seperate program for each library. + # Compile a separate program for each library. indentation...

Comment on attachment 118232 [details] [diff] [review] Revised fixes for seper* Please don't change the glib and libIDL stuff; that'll just make any future merges from or comparisons with the main glib tree harder. These aren't really part of mozilla proper: >Index: xpcom/typelib/xpidl/glib/glib-1.2.1/ChangeLog >Index: xpcom/typelib/xpidl/glib/glib-1.2.1/NEWS >Index: xpcom/typelib/xpidl/glib/glib-1.2.1/ltmain.sh >Index: xpcom/typelib/xpidl/glib/glib-1.2.1/gmodule/gmodule.c >Index: xpcom/typelib/xpidl/libidl/libIDL-0.6.5/ltmain.sh So remove the changes to those files, and assuming that the rest of your changes compile and test properly, sr=dmose.

Comment on attachment 118245 [details] [diff] [review] Really revised fixes for seper* Carrying over r=cbiesinger, sr=dmose

Comment on attachment 124248 [details] [diff] [review] Avilable fixes Brendan: Can you sr= or rs= this? Timeless mentioned that you or someone else might have rs='ed spelling changes already, but wasn't sure.

Comment on attachment 124248 [details] [diff] [review] Avilable fixes > =========== > > 1) start the server, with python server.py >-2) Get an file of all tests avilable by getting http://localhost:8000/ >+2) Get an file of all tests available by getting http://localhost:8000/ Since you're bothering to fix trivia, why not fix the incorrect article ("an file") too? This seems like the last thing to work on right now. It also seems like a lifelong hobby, unless you plan on automating. >--- nsTransferable.cpp 18 Apr 2003 20:20:00 -0000 1.59 >+++ nsTransferable.cpp 27 May 2003 01:41:14 -0000 >@@ -86,7 +86,7 @@ > void SetData( nsISupports* inData, PRUint32 inDataLen ); > void GetData( nsISupports** outData, PRUint32 *outDataLen ); > nsIFile * GetFileSpec(const char * aFileName); >- PRBool IsDataAvilable() const { return (mData && mDataLen > 0) || (!mData && mCacheFileName); } >+ PRBool IsDataAvailable() const { return (mData && mDataLen > 0) || (!mData && mCacheFileName); } > > protected: > >@@ -418,7 +418,7 @@ > > for ( PRInt32 i=0; i < mDataArray->Count(); ++i ) { > DataStruct * data = (DataStruct *)mDataArray->ElementAt(i); >- if (data->IsDataAvilable()) { >+ if (data->IsDataAvailable()) { > *aFlavor = ToNewCString(data->GetFlavor()); > data->GetData(aData, aDataLen); > return NS_OK; Ok, this is a better fix to make. Although were the interface ever a candidate for freezing (it's not frozen, right?), the typo would get fixed, I'm sure. /be

Comment on attachment 124250 [details] [diff] [review] Avilable --- Also changes an to a Carrying over sr=brendan

Comment on attachment 63787 [details] [diff] [review] a complete set of fixes for nspr Timeless is making a new nspr patch.

Comment on attachment 124250 [details] [diff] [review] Avilable --- Also changes an to a Checked in by dwitte

This is the only such misspelling of "Dropping" in /mozilla.

Comment on attachment 134227 [details] [diff] [review] patch for "Droping" typo in nsTimerImpl.cpp Once again, a typo inside a string. Too bad it's only one.

Comment on attachment 134227 [details] [diff] [review] patch for "Droping" typo in nsTimerImpl.cpp r+sr=darin

As requested by bug 99625. Thanks timeless for the cc there.

Comment on attachment 134486 [details] [diff] [review] patch for referingURI After careful consideration, I think it much better to fix all instances of "refering" in our source code. Patch coming up as soon as possible.

Comment on attachment 134538 [details] [diff] [review] patch for refering => referring Is there anyone I need to get moa from on this patch? (The spelling fixes touch almost entirely comments and non-executing strings.)

Comment on attachment 134538 [details] [diff] [review] patch for refering => referring As long as none of the flags being changed are frozen, sr=dmose.

in xpconnect: http://lxr.mozilla.org/seamonkey/search?string=garabage

Looking for fast r/sr for checkin before the tree closure. The fixes are all in comments, in one file.

Comment on attachment 134538 [details] [diff] [review] patch for refering => referring checked in by timeless.

Comment on attachment 135878 [details] [diff] [review] patch for garabage => garbage sr=alecf

rs=brendan on any spelling fixes. Maybe it would be better to get module owners to make these, so they know about 'em? Then the spelling fixers could focus on other, more productive work. /be

Could somebody take it to tree? BTW there are also this variations: http://lxr.mozilla.org/seamonkey/search?string=extenstion http://lxr.mozilla.org/seamonkey/search?string=extention

http://lxr.mozilla.org/mozilla/search?string=definately I might make a patch for this one later today.

Comment on attachment 145962 [details] [diff] [review] patch for "Unkonwn" -> "Unknown" r+sr=me and checked in for 1.8a.

*** Bug 221383 has been marked as a duplicate of this bug. ***

Also changes a bit of passive voice to active voice.

http://lxr.mozilla.org/mozilla/search?string=occured Unless occured is a British spelling, it really should be "occurred". I noticed this one in an XML error page for a missing XSL stylesheet.

Adam Lock noted an "editting" spelling in comment 6. There are still instances of that typo in three places under mozilla/editor (and ironically, in xpinstall/wizard/libxpnet/GUSI/include/GUSIFileSpec.h#9, mentioning this bug specifically).

Here are a *few* I ran across: http://lxr.mozilla.org/mozilla/search?string=allowded http://lxr.mozilla.org/mozilla/search?string=seperat http://lxr.mozilla.org/mozilla/search?string=extentions http://lxr.mozilla.org/mozilla/search?string=depreciated (not bug #93834) http://lxr.mozilla.org/mozilla/search?string=theres+ http://lxr.mozilla.org/mozilla/search?string=isntall http://lxr.mozilla.org/mozilla/search?string=unistall http://lxr.mozilla.org/mozilla/search?string=mozzilla http://lxr.mozilla.org/mozilla/search?string=+isnt+ http://lxr.mozilla.org/mozilla/search?string=+aint+ (some false positives.) http://lxr.mozilla.org/mozilla/search?string=+arent+ http://lxr.mozilla.org/mozilla/search?string=doesnt+ http://lxr.mozilla.org/mozilla/search?string=whats+ http://lxr.mozilla.org/mozilla/search?string=whos+ (whose?) http://lxr.mozilla.org/mozilla/search?string=firebird http://lxr.mozilla.org/mozilla/search?string=succesful http://lxr.mozilla.org/mozilla/search?string=sucessful http://lxr.mozilla.org/mozilla/search?string=favourite http://lxr.mozilla.org/mozilla/search?string=defualt http://lxr.mozilla.org/mozilla/search?string=obsevrer http://lxr.mozilla.org/mozilla/search?string=chnag http://lxr.mozilla.org/mozilla/search?string=peoples+ http://lxr.mozilla.org/mozilla/search?string=thats+ http://lxr.mozilla.org/mozilla/search?string=cosnt http://lxr.mozilla.org/mozilla/search?string=tuctor http://lxr.mozilla.org/mozilla/search?string=necesary http://lxr.mozilla.org/mozilla/search?string=neccesary http://lxr.mozilla.org/mozilla/search?string=+sting http://lxr.mozilla.org/mozilla/search?string=atuomatic http://lxr.mozilla.org/mozilla/search?string=supress http://lxr.mozilla.org/mozilla/search?string=+tru+ http://lxr.mozilla.org/mozilla/search?string=cotent http://lxr.mozilla.org/mozilla/search?string=frist http://lxr.mozilla.org/mozilla/search?string=contet http://lxr.mozilla.org/mozilla/search?string=alot* http://lxr.mozilla.org/mozilla/search?string=+alot http://lxr.mozilla.org/mozilla/search?string=wont+ http://lxr.mozilla.org/mozilla/search?string=colaps http://lxr.mozilla.org/mozilla/search?string=dont+ http://lxr.mozilla.org/mozilla/search?string=+eror+ http://lxr.mozilla.org/mozilla/search?string=erorr http://lxr.mozilla.org/mozilla/search?string=+erors http://lxr.mozilla.org/mozilla/search?string=debuging http://lxr.mozilla.org/mozilla/search?string=largst+ http://lxr.mozilla.org/mozilla/search?string=prefered http://lxr.mozilla.org/mozilla/search?string=srcipt http://lxr.mozilla.org/mozilla/search?string=retrun http://lxr.mozilla.org/mozilla/search?string=mesage http://lxr.mozilla.org/mozilla/search?string=reguardless http://lxr.mozilla.org/mozilla/search?string=speling My favorites, though, given my name... http://lxr.mozilla.org/mozilla/search?string=uknown http://lxr.mozilla.org/mozilla/search?string=unkown http://lxr.mozilla.org/mozilla/search?string=unknow+ -[Unknown]

I guessed that from the tring, but verified it: http://lxr.mozilla.org/mozilla/search?string=speling are all actually correct, changes would actually be bugs here. http://lxr.mozilla.org/mozilla/search?string=favourite is correct british spelling, so you might get into a flame war here ;-) Who will make up a patch correcting the real bugs here? Unknown, can you do that?

Alrighty. Needed a break from PHP anyway. I left, namely, MWLinker_MachO_supresswarnings and Firebird in many places. (a lot of bad filenames in help...) As well, I noticed the following other misspellings: http://lxr.mozilla.org/mozilla/search?string=protocal http://lxr.mozilla.org/mozilla/search?string=persistan http://lxr.mozilla.org/mozilla/search?string=coresp http://lxr.mozilla.org/mozilla/search?string=corellate http://lxr.mozilla.org/mozilla/search?string=teh+ http://lxr.mozilla.org/mozilla/search?string=mozila http://lxr.mozilla.org/mozilla/search?string=wheter http://lxr.mozilla.org/mozilla/search?string=+wether http://lxr.mozilla.org/mozilla/search?string=supend http://lxr.mozilla.org/mozilla/search?string=flaot http://lxr.mozilla.org/mozilla/search?string=realy http://lxr.mozilla.org/mozilla/search?string=+cant+ http://lxr.mozilla.org/mozilla/search?string=didnt http://lxr.mozilla.org/mozilla/search?string=completl http://lxr.mozilla.org/mozilla/search?string=arround http://lxr.mozilla.org/mozilla/search?string=recieved If I ran across one of these in the same sentence as one from the original list, I fixed it... I think there were all of three sentences I reworded for grammar. I did notice that some things were function names that looked possibly purposefully unchanged. The patch changes those (there aren't many anyway, and they can be taken out...) for the reason that, I believe, if Mozilla intends to get this publicly used as a toolkit (I seem to remember that being a goal?) having any misspellings in function names will be very detrimental, cause problems/bugs, and confuse people. Better to fix them now. As well, I noticed a few places (again not many) where these changes probably solved javascript errors in the browser itself. This patch was, notably, made for the trunk. -[Unknown]

(sorry, was bigger than 500k...) -[Unknown]

Apologies for the bug spam, more misspellings: http://lxr.mozilla.org/mozilla/search?string=depnd http://lxr.mozilla.org/mozilla/search?string=specifed http://lxr.mozilla.org/mozilla/search?string=specfied http://lxr.mozilla.org/mozilla/search?string=mvoe http://lxr.mozilla.org/mozilla/search?string=prevoius http://lxr.mozilla.org/mozilla/search?string=ackowledg http://lxr.mozilla.org/mozilla/search?string=equivelend http://lxr.mozilla.org/mozilla/search?string=equivelant http://lxr.mozilla.org/mozilla/search?string=eqaul http://lxr.mozilla.org/mozilla/search?string=atribu http://lxr.mozilla.org/mozilla/search?string=its+done http://lxr.mozilla.org/mozilla/search?string=editabel http://lxr.mozilla.org/mozilla/search?string=inotherwords http://lxr.mozilla.org/mozilla/search?string=argment http://lxr.mozilla.org/mozilla/search?string=agument http://lxr.mozilla.org/mozilla/search?string=decription http://lxr.mozilla.org/mozilla/search?string=langauge http://lxr.mozilla.org/mozilla/search?string=ojbect http://lxr.mozilla.org/mozilla/search?string=udpate http://lxr.mozilla.org/mozilla/search?string=genert http://lxr.mozilla.org/mozilla/search?string=funciton http://lxr.mozilla.org/mozilla/search?string=coment http://lxr.mozilla.org/mozilla/search?string=sourc+ http://lxr.mozilla.org/mozilla/search?string=quoet http://lxr.mozilla.org/mozilla/search?string=qoutes http://lxr.mozilla.org/mozilla/search?string=immplement http://lxr.mozilla.org/mozilla/search?string=tmeplate http://lxr.mozilla.org/mozilla/search?string=biuld http://lxr.mozilla.org/mozilla/search?string=temparar http://lxr.mozilla.org/mozilla/search?string=qeust http://lxr.mozilla.org/mozilla/search?string=wigdet http://lxr.mozilla.org/mozilla/search?string=reparetn (not sure what that's supposed to be...?) http://lxr.mozilla.org/mozilla/search?string=dcumentation http://lxr.mozilla.org/mozilla/search?string=suport http://lxr.mozilla.org/mozilla/search?string=class's http://lxr.mozilla.org/mozilla/search?string=columns's http://lxr.mozilla.org/mozilla/search?string=consistant http://lxr.mozilla.org/mozilla/search?string=sesion http://lxr.mozilla.org/mozilla/search?string=this's http://lxr.mozilla.org/mozilla/search?string=orignal http://lxr.mozilla.org/mozilla/search?string=corect http://lxr.mozilla.org/mozilla/search?string=connct http://lxr.mozilla.org/mozilla/search?string=exeption http://lxr.mozilla.org/mozilla/search?string=execption Further, this has a zillion results: http://lxr.mozilla.org/mozilla/search?string=favorit While this has one: http://lxr.mozilla.org/mozilla/search?string=favourit It may be correct spelling, but it's not *consistent* spelling. If that means making it ALL favourite, that works too - but two spellings used concurrently is bad. At least, in my opinion. -[Unknown]

http://www.m-w.com/cgi-bin/dictionary?book=Dictionary&va=corespondent m-w does not dislike that. btw thanks for picking this up. some people really do appreciate this work.

(In reply to comment #120) > http://www.m-w.com/cgi-bin/dictionary?book=Dictionary&va=corespondent > > m-w does not dislike that. btw thanks for picking this up. some people really > do appreciate this work. Heh, but did you read that? It says, basically, an adulterer. It doesn't like this, though: http://m-w.com/cgi-bin/dictionary?coresponding Because the word being used here has two r's, or at least it should. And, sure... should I create a patch with the next batch of words? Any opinions on favourite? -[Unknown]

/extensions/spellcheck/myspell/dictionaries/en-US.dic, line 12299 -- corespondent/MS that's a dictionary file, don't change it :).

Oops, class's and this's were right. But columns's should be columns' to my understanding. (has to do with syllables.) This patch should fix all the misspellings listed in comment #117 and comment #119 (minus this's and class's.) In theory, it doesn't conflict with the other patch - either, neither, or both could be applied. More misspellings I found making that patch: http://lxr.mozilla.org/mozilla/search?string=insenstive http://lxr.mozilla.org/mozilla/search?string=writting http://lxr.mozilla.org/mozilla/search?string=diferent http://lxr.mozilla.org/mozilla/search?string=pased http://lxr.mozilla.org/mozilla/search?string=+wich+ http://lxr.mozilla.org/mozilla/search?string=adress+ http://lxr.mozilla.org/mozilla/search?string=corrolat (attachment #146019 [details] [diff] [review]) http://lxr.mozilla.org/mozilla/search?string=interpet http://lxr.mozilla.org/mozilla/search?string=interepret http://lxr.mozilla.org/mozilla/search?string=interprt http://lxr.mozilla.org/mozilla/search?string=data+base http://lxr.mozilla.org/mozilla/search?string=desireable And, no, don't worry, I'm not dumb enough to change dictionary entries ^_^. I was referring to this: http://lxr.mozilla.org/mozilla/source/other-licenses/libical/src/libical/icalrecur.c#860 (I do realize that may be external, but why does that mean it should have typos ;)?) I'm sure my patches probably touch things they shouldn't... it's easy to take those things out though, it's considerably more work to make another patch for typos I left out because I assumed they would not be patched. (for one thing, cvs chews dirt for several minutes to make a patch, at least for me.) I assume from observation that, if I wanted any of these changes actually used, I should request review/superreview - is that correct? If so, from whom would be best? Thanks, -[Unknown]

Sorry, more bugspam, I guess... http://lxr.mozilla.org/mozilla/search?string=dependan http://lxr.mozilla.org/mozilla/search?string=refrence http://lxr.mozilla.org/mozilla/search?string=vlaues http://lxr.mozilla.org/mozilla/search?string=vallues http://lxr.mozilla.org/mozilla/search?string=+posible+ http://lxr.mozilla.org/mozilla/search?string=resposible http://lxr.mozilla.org/mozilla/search?string=aplicat http://lxr.mozilla.org/mozilla/search?string=+mising http://lxr.mozilla.org/mozilla/search?string=nuber http://lxr.mozilla.org/mozilla/search?string=+leter http://lxr.mozilla.org/mozilla/search?string=capitol+ http://lxr.mozilla.org/mozilla/search?string=modifc http://lxr.mozilla.org/mozilla/search?string=other+wise http://lxr.mozilla.org/mozilla/search?string=verficat http://lxr.mozilla.org/mozilla/search?string=droping http://lxr.mozilla.org/mozilla/search?string=additon http://lxr.mozilla.org/mozilla/search?string=arrray http://lxr.mozilla.org/mozilla/search?string=sytem -[Unknown]

Unknown: see comment 104, which is effective as a blanket super-review for spelling fixes that don't break stuff... so a r+ from someone should be sufficient. (And as timeless mentioned, some people love this. I'm one of them, but I've been busy...)

Unknown: I guess you can ask timeless for review, as he always likes such changes ;-)

Robert Kaiser wrote: > Unknown: I guess you can ask timeless for review, as he always likes such > changes ;-) I like such changes, too... and I am willing to r= such changes if I can verify them with http://dict.leo.org/ ... :)

Comment on attachment 149866 [details] [diff] [review] The misspellings I reported. (sans bogus, first chunk) Let's see if I can't do this right... I suppose there should be a way to request review on multiple, but I'd rather do one at a time anyway. -[Unknown]

More bugspam/misspellings: http://lxr.mozilla.org/mozilla/search?string=useable http://lxr.mozilla.org/mozilla/search?string=loged http://lxr.mozilla.org/mozilla/search?string=varables http://lxr.mozilla.org/mozilla/search?string=javascipt http://lxr.mozilla.org/mozilla/search?string=navagat http://lxr.mozilla.org/mozilla/search?string=qeue http://lxr.mozilla.org/mozilla/search?string=masqeurad http://lxr.mozilla.org/mozilla/search?string=editting http://lxr.mozilla.org/mozilla/search?string=widnow http://lxr.mozilla.org/mozilla/search?string=passowrd http://lxr.mozilla.org/mozilla/search?string=meseng http://lxr.mozilla.org/mozilla/search?string=stlye http://lxr.mozilla.org/mozilla/search?string=ammount http://lxr.mozilla.org/mozilla/search?string=sofware http://lxr.mozilla.org/mozilla/search?string=outputing http://lxr.mozilla.org/mozilla/search?string=layot http://lxr.mozilla.org/mozilla/search?string=bufer+ http://lxr.mozilla.org/mozilla/search?string=coppied http://lxr.mozilla.org/mozilla/search?string=porport http://lxr.mozilla.org/mozilla/search?string=securty http://lxr.mozilla.org/mozilla/search?string=thier+ http://lxr.mozilla.org/mozilla/search?string=/maping http://lxr.mozilla.org/mozilla/search?string=pading http://lxr.mozilla.org/mozilla/search?string=yelow http://lxr.mozilla.org/mozilla/search?string=backgrond http://lxr.mozilla.org/mozilla/search?string=suppot http://lxr.mozilla.org/mozilla/search?string=gramar http://lxr.mozilla.org/mozilla/search?string=asume -[Unknown]

useable is correct. Spelling changes are annoying, changing correct spelling is worse.

(In reply to comment #130) > useable is correct. Spelling changes are annoying, changing correct spelling is > worse. Possibly so, but it's inconsistent. While technically it is another spelling of usable, it's a much less used one and there's no reason to keep it in place of usable. http://lxr.mozilla.org/mozilla/search?string=usable (zillion results) http://lxr.mozilla.org/mozilla/search?string=useable (7 results) http://www.google.com/search?q=usable (2,560,000) http://www.google.com/search?q=useable (563,000) The word also reads more awkwardly. But, of course, it can be left.... I have no problem with that, myself. And, for what it's worth, spelling changes may be annoying but reading them is also annoying for many. Keeping the spelling mostly correct generally reduces confusion and makes things look more professional - everyone makes typos but only the ones who actually care fix them. It may not be terribly "outward" in most cases (usually just in comments) but that does not mean they are not seen and read. Some more: http://lxr.mozilla.org/mozilla/search?string=retreive http://lxr.mozilla.org/mozilla/search?string=smilie (it *is* smiley/smileys - more occurances of those anyway if you look.) http://lxr.mozilla.org/mozilla/search?string=eventualy http://lxr.mozilla.org/mozilla/search?string=finshed http://lxr.mozilla.org/mozilla/search?string=to+much http://lxr.mozilla.org/mozilla/search?string=acura http://lxr.mozilla.org/mozilla/search?string=likly http://lxr.mozilla.org/mozilla/search?string=sufix I've also noticed some grammar inconsistency - the same screen/panel will have checkbox labels with and without proper punctation. (but I'm not sure this in the scope of this bug.) -[Unknown]

(In reply to comment #131) > And, for what it's worth, spelling changes may be annoying but reading them is > also annoying for many. Keeping the spelling mostly correct generally reduces > confusion and makes things look more professional - everyone makes typos but > only the ones who actually care fix them. I regularly fix spelling errors *while* doing real code changes and correct them while reviewing. Note that I don't object to spelling changes, but they are annoying. And I don't think it's for you to decide how a word should be spelled, as long as the original author spelled it correctly.

(In reply to comment #132) > I regularly fix spelling errors *while* doing real code changes and correct them > while reviewing. Note that I don't object to spelling changes, but they are > annoying. And I don't think it's for you to decide how a word should be spelled, > as long as the original author spelled it correctly. Of course it isn't for me to decide - but, by no means should I just say "okay" when I disagree. That may be what a lot of people are trained to do, but it's the wrong thing to do. Whether or not you agree, at least now you understand why I listed it and points have been made - which you may or may not agree with. If it is preferred that words be left as is if they are not technically wrong, even if inconsistent (I suppose like smilie) that is, as always, fully possible. I have just always felt a great need for consistency in programming, because that is what makes everything flow together. And, say as you will that this is unimportant - but I found at least a few javascript errors and fixed them making the patches I have. Because of typos. Proper and periodic review is the easiest and best way to find these - as always, imho. You can't catch it *all* any other way. Inspired by my own typo, there's also: http://lxr.mozilla.org/mozilla/search?string=punctation -[Unknown]

Comment on attachment 149866 [details] [diff] [review] The misspellings I reported. (sans bogus, first chunk) If I attach short patches for each word, will I have a chance, or should I just not bother? -[Unknown]

http://lxr.mozilla.org/mozilla/search?string=reparetn (not sure what that's supposed to be...?) reparent

Comment on attachment 149866 [details] [diff] [review] The misspellings I reported. (sans bogus, first chunk) declear i'm not reviewing changes to build files or firefox, ask bsmedberg/mconnor. i'm reviewing changes to calendar. i'm reading but not sure i count as a reviewer for changes to camino, you might want to ask josh aas <joshmoz@gmail.com> i think cck is mostly orphanned and hope there's a rubber stamp we can use for commits to it. get dmose to sign off on directory get rginda/silver@warwick to sign off on chatzilla/venkman get pike to sign off on transformiix please split the boehm, zlib, and libical changes into their own patches >Index: mozilla/build/unix/print-depth-path.sh >+# It don't use Artificial Intelligence. It don't use Virtual Reality. perhaps: doesn't/g >+# It's not perl. It's not python. But it works. perhaps: Isn't/g >+ // this could call the account wizard, I guess that's a later feature perhaps: feature for later >Index: mozilla/cck/CCKDocs/cd_cck.htm >-Using a graphics editing program, open the <code>isntall.bmp</code> file and make your changes to it. For example, you might want to add your company's logo and name. that's depressing. > >+Using a graphics editing program, open the <code>install.bmp</code> file and make your changes to it. For example, you might want to add your company's logo and name. and on the wrong line? >@@ -413,7 +413,7 @@ > <em>installation_directory</em>\CCKTool\Configs\<em>my_config</em>\Workspace\Autor it'd be better if Autorun was together, split the previous line before the last '>'. >-un\Shell\bmps\isntall.bmp > >+un\Shell\bmps\install.bmp >Index: mozilla/cck/build/CCKBuild.bat >+REM IF _MSC_VER doesn't equal 1200 then VC+ is not version 6.0, VC++ > REM 6.0 is the standard so the build will not happen if _MSC_VER is > REM any value other than 1200! someone needs to file a bug about this... >Index: mozilla/cck/ib/ib.cpp > /*Post Beta -This is a hack to prevent the last page from staying up there endlessly; > We check to see if the filename is null and if it is so we return true perhaps change 'is so' to 'is' :) >- so that the return value isnt made FALSE */ >+ so that the return value isn't made FALSE */ man, this text sucks >@@ -2268,7 +2268,7 @@ > /*Post Beta - we will use the DISABLED key. > Now this is implemented the round about way here. > We have to take only the components that are chosen and mark the rest as disabled >-Disabled doesnt work now - so what we are doing is re writing every key in the sections >+Disabled doesn't work now - so what we are doing is re writing every key in the sections perhaps re-writing ? >@@ -3135,7 +3135,7 @@ > return TRUE; > } > //PostBeta - We have to inform the user that he has not set any value >-//and that it will default.Returning TRUE so that it doesnt stay in the last >+//and that it will default.Returning TRUE so that it doesn't stay in the last perhaps space after '.' ? >Index: mozilla/composer/base/content/editor.js >@@ -384,7 +384,7 @@ >- editorStatus = nsIEditingSession.eEditorErrorUnkown; >+ editorStatus = nsIEditingSession.eEditorErrorUnknown; hrm, does the iid rev for nsIEditingSession need to be bumped if you rename a constant? :) >Index: mozilla/extensions/help/resources/locale/en-US/mail_sec_help.xhtml >- <a href="#message_security_recieved_mesage">Message Security - Received >+ <a href="#message_security_recieved_message">Message Security - Received http://lxr.mozilla.org/seamonkey/search?string=message_security_recieved_mes you need to have changed all 4 spots, it doesn't look like you did. >@@ -2531,7 +2531,7 @@ > NS_PRECONDITION(!PyErr_Occurred(), "Expecting no Python exception to be pending when processing the return result"); > > nsresult rc = NS_OK; >- // If we dont get a tuple back, then the result is only >+ // If we don't get a tuple back, then the result is only // an int nresult for the underlying function. probably nsresult compare http://lxr.mozilla.org/seamonkey/source/extensions/python/xpcom/src/PyGBase.cpp #458 with http://lxorg/seamonkey/source/extensions/python/xpcom/src/PyGBase.cpp#481 >Index: mozilla/js/jsdj/classes/com/netscape/jsdebugging/ifcui/Emperor.java >@@ -233,7 +233,7 @@ >- _sourceViewManager.setPreferedNewViewRect( rectSrc ); >+ _sourceViewManager.setPreferredNewViewRect( rectSrc ); >@@ -410,7 +410,7 @@ >- _sourceViewManager.setPreferedNewViewRect(getPreferedNewSourceViewRect()); >+ _sourceViewManager.setPreferredNewViewRect(getPreferedNewSourceViewRect()); you missed a spot >@@ -541,7 +541,7 @@ >- private Rect getPreferedNewSourceViewRect() >+ private Rect getPreferredNewSourceViewRect() >Index: mozilla/layout/html/base/src/nsFrame.cpp >=================================================================== >RCS file: /cvsroot/mozilla/layout/html/base/src/nsFrame.cpp,v >retrieving revision 3.486 >diff -u -3 -r3.486 nsFrame.cpp >--- mozilla/layout/html/base/src/nsFrame.cpp 2 Jun 2004 02:25:18 -0000 3.486 >+++ mozilla/layout/html/base/src/nsFrame.cpp 2 Jun 2004 20:42:22 -0000 >@@ -1963,7 +1963,7 @@ > } > } > } >-#endif //XXX we USED to skip anonymous content i dont think we should anymore leaving this here as a flah >+#endif //XXX we USED to skip anonymous content, but I don't think we should anymore leaving this here as a flah flag >Index: mozilla/mailnews/compose/src/nsMsgCompose.cpp >=================================================================== >RCS file: /cvsroot/mozilla/mailnews/compose/src/nsMsgCompose.cpp,v >retrieving revision 1.431 >diff -u -3 -r1.431 nsMsgCompose.cpp >--- mozilla/mailnews/compose/src/nsMsgCompose.cpp 22 May 2004 22:15:11 -0000 1.431 >+++ mozilla/mailnews/compose/src/nsMsgCompose.cpp 2 Jun 2004 20:43:48 -0000 >@@ -1256,7 +1256,7 @@ > * If we don't call GC, the nsIMsgCompose object hold by JS will not be released despite we set > * the JS global that hold it to null. Each time we reopen a recycled window, we allocate a new > * nsIMsgCompose that we really need to be releazed when we recycle the window. In fact despite >- * we call GC here atfer the release wont occurs right away. But if we don't call it, the release >+ * we call GC here, the release won't occur right away. But if we don't call it, the release > * will apppend only when we phisically close the window which will append only on quit. physically > */ > nsCOMPtr<nsIScriptGlobalObject> sgo(do_QueryInterface(m_window)); >@@ -1277,7 +1277,7 @@ > if (m_editor) > { > /* The editor will be destroyed during yje close window. the >- * Set it to null to be sure we wont uses it anymore >+ * Set it to null to be sure we won't use it anymore > */ > m_editor = nsnull; > } >Index: mozilla/modules/plugin/base/src/nsPluginHostImpl.cpp >@@ -4826,9 +4826,9 @@ >- // If plugin changed, delete cachedPluginTag and dont use cache >+ // If plugin changed, delete cachedPluginTag and don't use cache > if (LL_NE(fileModTime, pluginTag->mLastModifiedTime)) { >- // Plugins has changed. Dont use cached plugin info. >+ // Plugins has changed. Don't use cached plugin info. should this be Plugin ? >Index: mozilla/mstone/Makefile >@@ -142,7 +142,7 @@ >+# perl is handled separately do to its size due

> If I attach short patches for each word, will I have a chance, or should I just not bother? try to keep patches under 2000 lines. :) that last patch cost me hours. and i don't look forward to reviewing the next chunks.

It took me even longer to make, and I still made mistakes :(. Sorry for wasting your time :/. >>+Using a graphics editing program, open the <code>install.bmp</code> file and make your changes to it. For example, you might want to add your company's logo and name. >and on the wrong line? I'm not sure I understand; it seems to me this is a watermark image? Wrong line? >http://lxr.mozilla.org/seamonkey/search?string=message_security_recieved_mes >you need to have changed all 4 spots, it doesn't look like you did. Like the idiot I am, I completely missed the "received" typo - this has since been fixed. I addressed all your comments (or so I think), up to a point and then stopped. I tried to skip the sections you suggested were better reviewed by someone else. 10 lines short of 2000. -[Unknown]

oh, i should have been a lot clearer about that one: that patch has: A-Using ... 2 B+Using ... what bothered me was that B was after 2 instead of between A and 2: A-Using ... B+Using ... 2 if that doesn't make sense, don't worry about it. i'm gone for the weekend and have other work i need to do so i won't look in for a while.

(In reply to comment #140) > that patch has: > A-Using ... > 2 > B+Using ... I noticed that too but didn't realize it was what you meant. The whole file is double spaced, and so I think it may have more to do with the line endings and how my cvs diff (cvsnt, cygwin diff I believe) is handling it. More specifically, I think the problem is it has \r\r\n line endings, meaning it's been double windows-atized (forgive me for making up a word :P.) -[Unknown]

Comments-only patch; there are two files this patch doesn't touch, because those files have live code with the typo.

Comments-only patch; there are two files this patch doesn't touch, because those files have live code with the typo.

Comment on attachment 165082 [details] [diff] [review] fix pseudo typos in comments only accidentally posted the same patch twice

Live code changes, need r and sr.

Comment on attachment 165086 [details] [diff] [review] fix pseudo typos in nsMessengerMigrator I think I got them all.

Here's another one. The double C is not "necessary". http://lxr.mozilla.org/mozilla/search?string=neccessary

Comment on attachment 165234 [details] [diff] [review] fix for spelling typos of neccessary -> necessary (comments only) This patch affects 29 files; fortunately, all the changed lines are either comments or in .txt or .html files.

Comment on attachment 165234 [details] [diff] [review] fix for spelling typos of neccessary -> necessary (comments only) r=dbradley These are all comment and readme file changes. I don't think it really needs a review, IIRC. And good catch on the necessarily as well.

Comment on attachment 165234 [details] [diff] [review] fix for spelling typos of neccessary -> necessary (comments only) Though this was checked in by timeless, there were apparently a couple parts of security code where the patch didn't apply.

Comment on attachment 165234 [details] [diff] [review] fix for spelling typos of neccessary -> necessary (comments only) the parts that didn't apply were gone. the bigger problem is that the partition was locked, so i didn't bother committing any of the security bits. i'll post a patch later and we can ask someone else to commit them.

Comment on attachment 165081 [details] [diff] [review] fix pseudo typos in comments only the layout files were moved; this patch needs updating