When doing a Search Messages you have the option to search in different fields. Here the "CC" and "To or CC" should be changed to "Cc" and "To or Cc".
Created attachment 13756 [details] [diff] [review] Fix that changed all references from "CC" to "Cc"
reassign all search/filter UI bugs to gayatrib, part 2
any chance for a checkin here? The patch has been laying around since 2000-08-30! Some feedback please...
Well, actually CC is an abbreviation for Carbon Copy. Also, abbrevations are always written with uppercase. Any objections?
You'll notice in the msgCompose window that we have it labeled as "Cc" and "Bcc". So I think it's fair that this should be changed, too.
r=hwaara now get someone to sr= this patch...
cc'ing bienvenu to sr= gemal's patch
The lib/libmsg code is dead - there's no reason to check that in. Also, this change is superfluous since we're already doing a case-insensitive comparison: - if (!nsCRT::strncasecmp ("CC", buf, end - buf)) + if (!nsCRT::strncasecmp ("Cc", buf, end - buf)) sr=bienvenu for the rest of the changes.
David, is it ok if we remove those lib/libmsg files then? Or just the code that gemal patched?
lib/libmsg is not part of SeaMonkey - I don't think it's part of anything (e.g., I don't think it ended up part of MozillaClassic either). You should check with leaf before removing it from the repository.
jglick/german: 4xp is Cc, but CC is an abbreviation, any objections before someone commits?
Don't check this in yet in any case, I'll ask leaf about getting rid of the lib.
Please help: Did we agree on "Cc" or "CC"? Håkan writes: "CC is an abbreviation for Carbon Copy. Also, abbrevations are always written with uppercase." I really dont care about what we write, as long as we write the same thing everywhere! If CC is correct, I'll provide the patches...
`Bcc' and `Cc' are easier to read and distinguish than `BCC' and `CC' are, because only the distinguishing letter is capitalized. And acronyms aren't always written in upper case, especially when they have been in existence for a while.
So we all agree on "Cc" and "Bcc" ?
Yes - agreed.
oops, failed to cc german. we're waiting for comments jglick/german.
"Cc" and "Bcc" are my preference.
As long as its applied consistently I don't care whether its CC:, cc: or Cc:, so yes Cc: and Bcc: and To: would be just fine.
checked in. reassigning to me to figure out what to do about libmsg.
I vote for CC for the reasons Håkan mentioned. "Cc" looks wrong to me - it's no normal word. FYI: RFC822 specifies "cc" (but "To"), so that would be fine with me as well.
BTW: I'm not arguing that you should back it out - there are more important things to work on.
We can worry about libmsg in a separate bug if anyone's interested. Closing this one.
Build 2001-04-02-04: NT4 Build 2001-04-02-08: Linux RH 6.2, Mac 9.04 Verified Fixed. The Search dialog now shows "To" and "Cc". I also see the same format in a new message/compose window.
*** Bug 212059 has been marked as a duplicate of this bug. ***