space
What I'm Writing
Thoughts on Writing and Technology


When I was writing an earlier blog, I ran it through the spell and grammar checker, and the grammar checker came up with three errors that weren't, and suggested three very ungrammatical fixes. At first, I couldn't figure out why, until I realized that I'd used a complex sentence structure with parallel subordinate clauses. Now, I obviously have nothing against technology per se, but this incident got me to thinking about the implications... and to a writer like me, those implications are between annoying and frightening.


It's clear that the software doesn't work nearly so well with complex phrases. Is that because it's not worth while to design it to that level of complexity? Or that it can't be? Either way, the end result isn't good, because it's applying simple rules to complex phrases, and that's one of the biggest problems with most technology, especially when the user understands neither the entire field in question nor the limits of the technology. But, as in the case of word-processing software, technology often allows the marginally competent to look like the competent -- until something really goes wrong.


These days, more and more young writers are relying on software to clean up their work, and every time I read manuscripts for a contest [which I do upon occasion] I'm reminded of this... and the fact that very few of them truly understand their native language.


Another problem that plagues me is the autoformatting feature of Word, especially when I have to go back three lines and put in a hard return so that I don't end up with an after-the-fact indented paragraph. I mean, after all, I didn't indent that paragraph when I typed it out. The software all of a sudden undid -- or redid -- what I did because I didn't conform to its programming. This is a recurring problem with all computer-based systems. They do what you tell them to do, not what you intended to do, and, sometimes, they even do something that you had no idea they could do, and that you certainly didn't plan on. The problems begin when there are features you don't know are incorporated in the system. You think you've told the system to do one thing, but your instructions are reformulated by the system. This is an annoyance in word-processing, but it can be a disaster, as in the case of the Mars probe that crashed because there were conflicting measurement systems programmed into the navigation systems, systems of which some of the scientists programming the deceleration were unaware.


And, of course, just about the time I've finally worked through and understand most of the glitches in a system, some hot-shot programmers and profit-motivated executives re-design the software... and before all that long I'll be forced to learn another new and improved system with unknown quirks or glitches, whether I want to or not, because sooner or later, things like the latest printers don't have printer-drivers for the old software, and because I tend to burn through printers, that limits my choices. And that irritates me, especially since "new" is often not better. I can count on it to be more complex, but not necessarily better, and certainly not simpler... and that's unfortunately true of most technology.



Comments:
As a writer (in progress) and a software engineer, I think I have an opinion here. ;-)

As a writer, I don't use grammar checkers. I like to think my education and command of the English language trumps any such engine's ability to perform corrections for me. Also, as you state, they often cannot interpret sentence structures beyond a certain complexity threshold. I often find the grammar checker in Word, for example, pointing out things that I know are just fine the way they are. Sometimes I even like to push the boundaries a tad and break some rules. I don't need a grammar checker to tell me I'm wrong in those cases.

As a software engineer, I understand the complexities of natural language processing (of which I believe a grammar checker falls under). A lot of it comes down to the programming tools available to us--they simply are not that good when it comes to such things. Now, it has been a while since I've done anything remotely close to NLP, so I could be wrong. But I've no doubt it's a very complex problem to solve. We'll get better, though, over time. Technology always does.
 
And yet, you're using a computer and word processor!

Surely, a typewriter is much simpler, could still do the job, and should thus be your obvious choice? No? ;)
 
Perhaps I should have clarified things more. I like new technology, at least once the bugs have been ironed out. I'm getting awfully tired of update after update of what amounts to incremental changes of an existing product, all of which updates require additional purchases, and which generally often few real changes but much greater costs and complexity.
 
Word has it's problems, but it sure beats the old fashioned typewriter. I actually think Word '07 is an improvement over the earlier versions, but i also don't like the auto-formatting and auto-correcting. It should be possible to turn those features off, in the preferences menu.

As for printers, I'd suggest the business laser printer option. I laugh at work every time the printer tells me 'Time to order new cartridge: 3000 pages remaining.' And in two and a half years, that printer has never broken. Being a hospital, we use a LOT of paper. Limitation is that it's only black and white, but for manuscripts, that would work.
 
Another software guy here. Not a writer but I often need to write technical documentation - and I absolutely hate MS Word for that. I'll use some plain text format where you can just focus on the content without the formatting features getting in the way.
It has the other advantage of universal compatibility - unlike a word document a .txt file will likely be readable by software for the foreseeable future. This is the reason the Gutenberg Project insists on having its content in plain text as a base format.
 
A professional writer should use a professional-quality spelling and grammar checker. The one that comes with Microsoft Office products is not adequate. I turn off application-linked or operating system checkers and use a dedicated product. Currently, I use Grammarian Pro X (for Mac OS X) from Linguisoft. It has multiple dictionaries (basic, technical, scientific, medical, legal, etc.) and, of course, a customizable user dictionary. It has pre-built grammar checking styles (casual, formal, business, academic, legal, etc.), but it is completely customizable: you can activate or deactivate any rules. If you never mix up there-their, then turn the rule off. If you don't want to be nagged about passive verbs, then turn that rule off. You can also, by application, turn interactive checking (spelling, grammar, or both) on or off.

Grammarian is not perfect: it, too, can give wrong grammar advice under some circumstances. This doesn't annoy me: I glance at the screen, see that Grammarian is wrong, and click the Ignore (or Ignore All) button. But, overall, Grammarian saves me time and embarrassment. The extra dictionaries mean that I don't have to spend time making a massive user dictionary. The universality (it works with everything) means that I don't need to make multiple user dictionaries. And the flexible grammar rules keep me from being nagged about casual usage when I'm writing a letter to a friend. I recovered my $50 investment in just a few weeks.
 
Post a Comment



<< Back to all Blog posts

 

News & UpdatesMonhtly QuestionsBlog Entries
www.LEModesittJr.com  |  Terms of Use  |  Privacy Notice