When I studied in Melbourne University, I was outraged at the rude graffiti I discovered on virtually every toilet wall. Almost all if it was sexual in nature, and I always felt it encouraged violence towards women or towards men perceived as not strong enough. This latter tendency was aided by the fact that as a university student at the end of the 1990s I had strong memories of bullying both at school and on the street.
Coarse (or violent) language on films or in music seemed to me like a natural culprit for bullying behaviour. When I first heard of film ratings, I presumed their purpose must be safety — preventing children learning that violence is acceptable behaviour or naïvely thinking thus.
At the same time, I was learning to use Microsoft Word, and one function I quickly discovered was AutoCorrect. I quite quickly began to check spelling on World, and soon discovered that I could add to and delete from AutoCorrect. Given my dislike of rude language, it felt entirely natural to add to AutoCorrect any rude word whose meaning in less coarse language was known. I did this a lot for a while, often repeatedly because my additions in the Melbourne University computer laboratories were probably not retained when the computers shut down at the end of each day.
All seemingly went well for a while, until I made, merely testing, a discovery that was truly shocking — that AutoCorrect was not case sensitive! This meant that “Dick” was corrected even when intended as someone’s name (I intended and assumed it would only correct when uncapitalised, but was shocked when “Dick Tyldesley”, a former Lancashire bowler, became “Penis Tyldesley”!). Following this, I assumed that the inability of AutoCorrect to be case sensitive meant computers really were not nearly so intelligent as everybody presumed. I consistently laughed at how something so specialised as a computer could be unable to distinguish capitalised from uncapitalised words and (in this case) correct only the uncapitalised. At the same time my brother said, critically but not aggressively, that by adding swear words I was turning AutoCorrect into “AutoCensor”. “AutoCensor” remains a really funny joke, much less gratuitous than the renaming of people called “Dick” by an addition intended only to AutoCorrect with a small initial letter.
After a while, the contrived nature of my additions to AutoCorrect made me think my original idea was silly because it was so difficult a job to accurately rewrite rude words as something less nasty and more often than not grauitously violent.
Then, I was told rather quietly one day by a university official than I had been banned from the computer labs for “tampering with AutoCorrect”. I was told that my tampering with AutoCorrect had ruined some other student’s essays — completely changing texts in such a way that they could not be mended. Unlike later cases at RMIT where I reacted extremely violently and angrily, I accepted this punishment because I knew very clearly that I had been altering AutoCorrect. Even if I felt my intentions were good, I had already realised that tampering with AutoCorrect simply could not do what I wanted it to.
Until recently I largely forgot about this, although I still thought of computers as really stupid because AutoCorrect was not and could not be made case-sensitive as I always assumed it should be. However, a discussion with my brother confirmed what he had said to be a quarter of a century ago — that AutoCorrect exists purely to correct typos, and is not designed to correct swearing (my brother’s “AutoCensor”). Although it ought to be simply enough to have separate AutoCorrect entries with different capitalisations, that has never been done because it would be more complex and the purpose was and is always corrections whose necessity is independent of capitalisation. If that be recognised, then computers that correct “Dick” when capitalised are simply doing what they are ask, whether it was my intention or not, and are not totally stupid as I have always thought!
No comments:
Post a Comment