16 January, 2012
Testing LibreOffice

Trying out LibreOffice for the first time so this may not be the most spirited or interesting journal entry that I've ever posted, which is a good way to start these things off, by the way. Don't worry. Nothing to read here. Move along.

Or, stick around. Hear the tale of how I discovered LibreOffice. Got to love that name. Wasn't planned, I understand. Just sort-of happened, but I'm not going to tell you the story of LibreOffice.

I've been using for those people who haven't been keeping track. Just didn't want to spend the bucks on the latest and greats version of Microsoft Office. I've been quite vocally of the opinion that Microsoft Office really kind-of peaked with Office 97. It's all been downhill since then what with one improvement and modification after another. Simply can't leave well enough alone. I limped along with Office 97 for years and years and years. Refused to upgrade. Couldn't stand what they had done to the place.

Finally had no choice. Really, they simply were not going to support Office 97 any longer, and it really kind-of wasn't going to work with the new operating system any more. Okay, maybe if I had put some effort into it. Maybe it would have worked. What did I know? Didn't bother trying to find out. Simply didn't bother trying to install it.

Did a bit of searching online. Discovered I had some version or other of Wordperfect installed on my computer. Turned out that it had been installed since the day I had purchased that computer. Remembered the days when Wordperfect had been the best word-processor out there. Tried it out. Yeah, go find the journal entry or two I tried to write using Wordperfect. Didn't go well.

Learned two things in my searching, which actually happened some indeterminate amount of time after I had discovered that copy of Wordperfect on my computer. Probably happened when I upgraded my computer. Can't remember. Probably the same computer. Not important enough to be a significant event in the life of this story.

I learned that there were web-based word-processors. This was just a bit before Microsoft and Google decided they needed to purchase all of the web-based word-processors out there. Not long before. Actually, I may have searched and discovered web-based word-processors at the same time I started experimenting with the copy of Wordperfect on my computer. Again, this is a rather unimportant detail. Just ignore.

Two problems with web-based word-processors especially in the early days but still kind-of continuing in my limited opinion and understanding of how these things work. First, they were awkward and clunky being web-based and all of that. Formatting was little more than what could be done on a standard web page. Very limited. Very slow. Prone to crashing, which I guess I could call a thing onto itself but I simply don't want to. Second, they were web-based. Everything written on them was stored in that wonderfully secure environment known as the world wide web. This really filled me with a great sense of assurance and security. Absolutely nothing ever gets hacked or stolen from out of the web.

I understand that things really have improved in the world of online word-processing and spread-sheeting since those long ago days of experimentation with Wordperfect, and this ends the nested portion of my point making. I just realized that I'm using nested points. Weird. Just the kind-of thing you never think about until you stumble across it. People probably use nested points all of the time and nobody ever notices. I mean. Why should people notice? It's just a natural part of human life. Nested points are good, I guess.

The second thing I learned in my searching after discovering a copy of Wordperfect on my computer and trying out those outdated versions of web-based word-processors was that there were open-source word-processors. Or, one open-source word-processor, anyway. Okay, I probably noticed that there was more than one, but the option that really stood out in my mind was Not entirely sure why. Probably the name. More likely the fact that it was sponsored kind-of like Firefox was sponsored. Is it still sponsored, by the way? I wonder about that on occasion. Is Firefox still sponsored by AOL or was that really just the Netscape 6 version? Maybe, Firefox broke away at some point or something. Maybe, the open-source version of Netscape 6 had another name. Can't remember. I suppose I could look it up on Wikipedia if I really felt like it. Not going to but I know that I could.

Anyway, I checked out It worked okay. Did what I needed. Didn't crash left and right. Had a big company sponsor so I kind-of figured that updates would continue on something resembling a regular basis. Everything was going about as well as these things could be expected to go.

Then, another company bought the first company. Didn't worry too much about this. The new company had as much interest in undermining Microsoft's stranglehold on the word-processing market as the old company. I wasn't overly worried. Noticed when the latest upgrade included some basic cosmetic changes to include the new company's name. No big deal. Program still worked. Could have gone on like this forever.

Was reading the comments on a post that Wil Wheaton had posted on his website or blog or whatever in the world they are calling these things nowadays. I swear that's a rant I don't need to get into right now. The whole I'm really rather unimpressed by the word blog rant. People always naming things. But, I shan't digress. The important bit being somebody or other mentioning a little thing called LibreOffice. The fact they were complaining that LibreOffice kept crashing was really rather unimportant. The bit that caught my attention was the basic idea there was another Office suite out there that just might be of the open-source persuasion and just might be free of big company sponsorship. Worth looking into.

Which brings us around to LibreOffice. Not going to get into the story of LibreOffice, but it did make me realize that it had been quite awhile since I had noticed the last update to Started to make me wonder when there would be another update to

Thus began the great debate in my poor overclocked little head over whether I should switch from to LibreOffice. Since I'm currently typing up this here little journal entry in LibreOffice, I think we all know how that debate ended.

22 January, 2012
Spoken Versus Written Rhythm

The best part of my little test of LibreOffice last week was that wasn't even close to what I had planned on writing about. I had actually had something on my mind. Sure, just one of those things that probably wouldn't interest anyone other than my own little self but that's hardly the point. I had actually had something I thought I could ramble on about, which doesn't happen as often as I might like. It's that whole dilemma I refuse to stop going on about.

I want updates on my website. Stagnation is death and all of that. Sure, I've got no reason to believe that anybody is paying attention to the website; therefore, it don't matter none if it's updated. Hardly the point. Stagnation is death, as already stated at the beginning of this paragraph.

However, I don't want updates just for the sake of updating. That's even worse than stagnation. Boring people out of their minds with the shear triviality of the updates. Good way to drive people away even faster than a stagnated site.

My dilemma and I won't shut up about it. Shows why I can get so excited when I do think of something I'm vaguely interested in writing about here. Having a topic. Oh, joyous rapture.

So, what the hey? Basically rehashed the story of picking a word-processing program. Oh, well, it was something to write about. Kept my focus and attention and all of that. And, oh, look. Once again, I haven't gotten to my topic. Shocking that.

Probably just goes to show in my heart of hearts that the thing I wanted to write about can't really be sustained for more than a sentence or two. State the idea. Discover the simple statement of the idea is all I've got. Panic. Wondering how else to fill the page. Don't really want to post short journal entries. Seems so trivial. That's what Facebook, Google Plus and Twitter are for.

So, maybe that's just exactly what I need to do. Post short journal entries for a change. Could grow something from that if only I gave it the chance. People probably hate these pointlessly meandering and disjointed journal entries as much as anything else. Short entry. Just go with it, right?

Anyway, I've been going over the few scenes I've actually written of the Shakespeare project with the intention of actually writing more of the damn thing. All part of shaking the dust off and all of that. Work the kinks. Stretch. Get in the groove. Etc.

Anyway, I keep rewriting the third line of the first scene. Going back and forth between two options. "It is true" and "It's true." Yeah, seriously. No idea how many times I've scribbled one out and written the other. Just one of those things that matters to nobody other than my own little self, but it is important. Right at the beginning. Those first few lines are rather important. Strong desire to get them right.

Okay, as can be discerned from the wording options, it is a line of dialogue, and it's been driving me nuts. Go with the more formal or the more natural. Every time I imagine the line being said, I want to use "It's true." Every time I read the line, I want to use "It is true."

Now, this has nothing to do with characterization or what this particular character would actually say. I know, sure. You can tell a lot about character based on whether they are more or less likely to use contractions. But, here's the thing. It don't matter none. Even people who are more likely to use one than the other can on occasion use the one they typically shy away from. Context is really important and all of that. If I universally made sure the character used one and absolutely never used the other, that would feel incredibly contrived and artificial.

I guess you could say there's a real art to this. Knowing when to display a character tick and when to let the natural flow of the moment carry the text along. Thus, the writer goes insane over things the audience probably never notices, creating yet another wild monstrosity for the poetry hunters to track.

So, I scribble one. Read it again. Scratch out. Scribble the other. And, it's not even about character. This is a case where establishing character through the use of a contraction or not is utterly irrelevant. The concern here is flow. Feeling whether it is more natural to use the contraction.

I've even resorted to reading the passage aloud, and every time, I use the contraction. So, I scribble in the contraction. It's just more naturally spoken. Then, I read the passage over. Scratch out the contraction. Write both words. Speak it aloud. Or, really, just think speaking words as I read it over and know the contraction is what would be used.

Really, we've got wild poetry in the making here, and it's not even a poem.

Finally had a brainstorm, and I suddenly understood the problem. We're about to get seriously into the arcana of writing here. The kind-of thing that most of the universe and everything in it probably never even considers. Or, I'm just being pompous. Take your pick.

It's all about the rhythm, and the spoken word and the written word have different rhythms. Seriously, true. Reading something is different than speaking it. They flow differently. This is why so many writers will tell you they say the lines aloud after having written them to make sure they actually flow as speech. Very important for something meant to be spoken. Movies, plays and television and things like that. Why you can say something sounds very artificial. The written word wasn't properly evaluated for it's spoken rhythm before it reached an audience.

Thing to remember is that the spoken rhythm is not automatically more important then the written rhythm. They both have their place. Important to remember, and the heart of my brainstorm.

While "It's true" is more naturally spoken and more than likely what the character would have said under the circumstances, the contraction simply doesn't fit the rhythm of the written scene. It needs "It is true" for the flow to work. Amazing. Glad I finally recognized the problem. Simple solution, too. Accept the rhythm that works for the situation.

This Shakespeare project is a written work meant to be read. While a spoken version may or may not occur at some point given the natural order of world events, this version is intended to be read. Not even out loud. Read in the quite corners of one's mind.

So, I've plunked down "It is true," and I have absolutely no intentions of changing it at any point in the foreseeable future. The unforeseen future will just have to fend for itself.

And, there's not much chance I'll get hung-up on the language should there ever be a spoken version. Just take a look at the written version of The Faire Folk of Gideon and compare it to the audio version. I made changes to fit the flow of the spoken word all over the place in that one.

Of course, I don't know anyone who has admitted to listening to it so I don't really know how well that worked out. I know what I think of it, but that hardly matters. Anyway, contemplating the great audio ham that I am is a topic for another day.

Now, go away.

copyright © 2012 by keith d. jones – all rights reserved
home | books | music | fiction | spoken word | comics | journal | news