|
|
| Re: ESPN Fires Editor, Suspends Anchor (Was: Racist ESPN headline) (911032) | |||
 |
|||
| Home > OTChat | |||
|
[ Read Responses | Post a New Response | Return to the Index ] |
|
||
|
Re: ESPN Fires Editor, Suspends Anchor (Was: Racist ESPN headline) |
|
|
Posted by SelkirkTMO on Sun Feb 19 19:20:14 2012, in response to Re: ESPN Fires Editor, Suspends Anchor (Was: Racist ESPN headline), posted by Easy on Sun Feb 19 19:03:48 2012. I suspect that the mobile headline was probably unintentional as well, perhaps his phrase made it to the edit desk and they just flung it in there with the rest of what had to go out. I wouldn't necessarily blame the writer, but would definitely whip them. The real blame here lies with the editor since the job of an editor is to be the final arbiter of content and gatekeeper for the stupid. Editors read and approve the end product, writers tend to be too busy to think. Editors get PAID to think.Like I said though in my other reply here, "chink in the armor" shouldn't be considered offensive unless it was in caps or with elipses since it's not the same concept as "chink" by itself. Reminds me of a word that is no longer in use which had a crisp and precise meaning that can no longer be said because some people are "ignant" known as "niggardly" which has now vanished from the language as a result. This whole hoohah reminds me of Chicago sportscaster Harry Caray and his world-famous phrase, "Holy cow" ... if the Cubs had a Hindi pitcher, we'd probably be going through all this earlier, and it would be just as stupid as this hoohah ... offense should be taken in context of the meaning in my eyes. This time, it appears to be out of bounds. Are we going to end up with a language in which the only two acceptable words are "oooh" and "ahhh?" :-\ |
|
|
|