Search This Blog

Showing posts with label allegory. Show all posts
Showing posts with label allegory. Show all posts

Sunday, October 3, 2010

Review: Earthbow: Volume 2 by Sherry Thompson


Earthbow: Volume 2


ISBN: 978-0982508787

As the name suggest, this book picks up where Earthbow, Volume 1 left off. And the reader will be confused if they start with this book. Things will make a lot more sense if you get a copy of Volume 1 to read before reading Volume 2. If you haven't read either, the full story is worth the purchase price.

Why? Because this story continues to track the personal journeys of Harone, Coris, and Xander as they struggle to fight the evil threatening to consume the Narentia lands. And the situation does appear hopeless. And that's where the real battle plays out. For our heroes, this is a tale of self-sacrifice of the highest kind.

And this is not a book for the feint of heart. People die, sometimes in ways that make you wince. You don't get gory detail, but the evil is real, and threatening. You feel their struggle, and you sense their despair. And you watch them rise to the occasion, even when all seems lost.

It is a book of inspiration, that even in our darkest hours, we are not without hope.

I enjoyed the characters in this volume, as I did in the first. I liked seeing Xander discover his place in the story. The interaction is well done between the characters, and each had a story to tell.

As in the other books, the writing painted good pictures for me to see clearly what was happening. The descriptions gave a solid sense of setting and mood. There's a lot going on in this story, though it gets pulled together more in this volume than in the first, as threads come together, and the story boils down to the final face off with the enemy. The tension runs strong through the book, and culminates in a satisfying manner, that not only leaves you with a sense of resolution, but the meaning behind it sticks with you, and I found myself thinking about those events for days after reading it.

I gave the first volume a five star rating. After reading Volume 2, I found my five star rating wasn't wasted on a lackluster ending, and I can confidently give this one a corresponding five star rating as well. Which means, if you like a great fantasy story, you'll not go wrong in reading the whole set of these books, beginning with Seabird, Volumes 1 and 2, and Earthbow, Volumes 1 and 2. You can thank me later.

And I hear there is more stories in this world coming out. Your time in this world will give you a return, both in entertainment and enlightenment.

Note: The author gave me a copy of her book to review.

Monday, August 2, 2010

What's With the Hebrew?

For the second installment on the allegories in the Reality series, I wanted to talk more about the ring. Eventually, I'll talk about the allegorical nature of the ring itself, once the final book in the series comes out later this fall, and some time has passed. Meanwhile, there is one aspect of the ring that early on received comments.

For those not familiar, the first chapter/short story in the novella, Infinite Realities, tells how Sisko gains the ring, which as the priest says, marries him to God much as Sampson's hair created a vow between him and God. The ring Sisko gains in the mystical steam house enables him to be his "brother's keeper" by helping others with his new abilities to heal and perform miracles. And like Sampson's warning to never cut his hair, Sisko is told to never use the ring for his own benefit or it will become a curse instead of a blessing.

The words inscribed on the ring, which the priest reads, are the words of Christ, "It is more blessed to give, than to receive." And as the story relates it, these words are inscribed in Hebrew on the ring. That's why you see the Hebrew infinitive forms "to give" and "to receive" printed on the cover of Infinite Realities.

Early on when fellow writers critiqued that first story, someone mentioned the fact that Christ would have said those words in Aramaic or Greek, not likely Hebrew. And though it is entirely possible He could have said them originally in Hebrew, I agree, He probably used one of those two languages. Most likely Aramaic since that was the common tongue at that time in Israel. And I received that comment more than once from different people.

So, why did I use Hebrew? Did I have a reason? Oh yes! I did.

First, the practical consideration. Yes, it is unlikely Jesus used Hebrew when he said those words, and you won't find them exactly like that in the Old Testament, so He wasn't directly quoting Scripture. My response: and your point is...?

Think about the premise of the story here. Jesus isn't talking, rather God inscribed those words on the ring for a reason. He could have used any language in the world. He might have used German, or Swahili. It could have been anything. Because Jesus originally said them in one particular language wouldn't restrict God to use that one language, within the context of the story. So what language Jesus used initially has nothing to do with what language can be on that ring. Using a different one doesn't violate any historical reality. And, need I remind you, this is after all, fiction.

"So, dear author," I can hear you asking, "why did God use Hebrew to inscribe those words?"

Good question. Thanks for asking. In my mind, God chose Sisko to bear that ring. Hebrew is the language of God's chosen people. By using Hebrew, it analogically and allegorically signifies that God chose Sisko to bear the ring and fulfill that mission.

Warning, a bit of a spoiler coming up on Transforming Realities, but I'll be as general as I can to make the point.

Now, let's take this a bit further. In my novel sequel, Transforming Realities, toward the end of the book one of the results for Sisko's son being in the steam house is obtaining an ability, but it also causes him to be dependent upon his sister to both activate it and deactivate it. The first draft of that created some interesting reactions among those critiquing the story. Most didn't like it because they felt it bound the poor lad against his will to the whims of his sister. I think nearly everyone who critiqued it didn't like it.

I did a few things to lessen the negative affect on the reader, created a positive sense that Nathan liked this ability, and had a choice to accept it, though he couldn't reject it without some consequences. And while that helped, I think the general consensus was an uneasy feeling that Kaylee had that much control over him.

But in the end, I left it that way, and it relates to the fact that God chose Sisko to wear the ring above. Because Sisko didn't really have a choice either. God put the ring on him, and he couldn't pull it off. God didn't bother to stop and ask him if he wanted this mission. Yet this ring, as the priest said, married him to God's will in this matter.

No one balked at that situation. Why? I think it's because in Sisko's case, he is bound to God. In Nathan's case, he is bound to a human, his sister. And our reaction to that tends to run deep, especially in our individualistic society. We don't want to be dependent upon anyone, and rugged individualism is most often seen as a good thing. To have someone be put under the control of another hits our image of independence right where it hurts. We would rather not be forced to deal with that.

Before someone accuses me otherwise, let me say I'm not excusing one's responsibility to do for themselves what they can, and help out each other as often as we can. But the truth of the matter is that each of us is enslaved to another in one form or fashion, and according to the Bible, we are required to live out our lives by loving one another. And what is love but the total giving of ourselves for another person? Is it not enslaving ourselves to them? Is it not martyrdom of our lives to benefit another?

"But that's a willing enslavement," you might say. Hum, you think? Once you say "I do," it's supposed to be for life, and yet frequently isn't. A boss tells you what to do and how to do it. You are forced to do so if you want to make enough money to live. You may not even do that out of love. And yet, all labor is a form of slavery. Some freer to come and go as they please, but you give hours of your life to benefit another so you can feed and put a roof over yourself and maybe a family. Circumstances put us at the mercy of others, whether it is cancer entrusting us to the wisdom of doctors, or an earthquake destroying all we have, and we are forced to seek out help to survive. We are even enslaved to our government, which most of us didn't ask for, and required to pay taxes.

And do we need to go down through the pages of history and look at all the different forms of slavery? No, we cringe at the idea of another having authority over us. So much so that St. Paul's words in Ephesians about wives and husbands still ruffles the feathers of many a church goer.

But the bottom line is that Christ said, "In as much as you do it to the least of these, you do it to Me." And the least of these includes also the greatest of these, whether that is a rich boss, a overworked spouse, a screaming child, a beggar, or a dying friend. In as much as you show your love to these, you are enslaving yourself to Christ. I would even go so far as to say, that unless you are willing to be enslaved by another, you will fail to be a slave for Christ.

"But they might abuse me! Take advantage of me!" Yes, they might. Get out of destructive relationships if at all possible. Loving a person doesn't mean enabling them to continue with behaviors that are destructive for their souls and those around them. Indeed, your enslavement to them demands you want what is best for them, which may be counter to what they say they want. But we are still called to love, to fulfill whatever the calling, ministry, or investment into each others lives that we are given the means and ability to do. For God has chosen it for us.

That's why the inscription is written in Hebrew in my story. It's because God chose Sisko. Sisko didn't chose to bear the ring or become a miracle man. Just as Nathan didn't chose to be bound to help his sister. But he did so out of love for her, and the "bond" turned from a "have to" to a "want to." If we are not bound to another in some form or fashion, we don't love Christ as we ought. And we would do well not to shy away from the mission God has given us, but embrace it with faith in our Master, even if that calling entails a human "master."

Tuesday, May 18, 2010

Describing Description Detail

On this third and final day of the CSFF Blog Tour, I thought I would offer up an article which arose from discussion of my review of Jill Williamson's book, By Darkness Hid (see previous post). Jill painted some very vivid scenery settings that added to her story, but in my review I also mentioned that I tired of telling us what everyone was wearing, whether it fed into the story or not. The question arose in my mind, how do we decide what level of detail in our descriptions is "just right"?

Now, to be honest, one could make the case that what people are wearing is part of the scenery as well. And I would acknowledge that point. And I also understand that in a high fantasy such as this book, such level of detail is expected. But as I also pointed out in the comments, not even the high fantasy king himself, J. R. Tolkien, gave us much clues what his characters looked like beyond some bare descriptions.

For instance, when Gandalf comes on the scene, he only is described as wearing a long cloak, a pointy hat, and big, bushy eyebrows that (strangely enough) stick out past his hat's brim. I've always had a hard time viewing that. But it clearly says, "eccentric, old wizard coming." And for Frodo, you'd be hard pressed to find any description of him at all. You have to rely upon what Tolkien describes in the prologue about Hobbits in general, but that still doesn't tell you what Frodo looks like. The more important the character it appears, the less description they get with Tolkien.

To sum that up, the level of detail in a story is primarily a preference thing, both for the author and for the reader. Some want you to paint the full picture in every detail, others don't want you to slow down the story with minute detail. There's a balance each author has to find that works for their fans.

That said, there are some considerations an author should take into account when on how much detail to use. There are several factors that could change what you do.

Type of Story - If your writing an action story, you'll want to keep the descriptions down to what is absolutely needed to tell the story. Extra descriptions will slow things down unless you are skilled enough to relate that info while "in action." But even that can get too much. By definition, when a character is fighting or running, etc., they are so focused on what they are doing, on their opponent, that they don't notice the scenery, what people are wearing, etc. So putting much detail into such a scene would cause it to feel unreal.

Likewise, if your story is a character-based story, descriptions become important. You can set mood and foreshadowing with good descriptions, not only of surrounding scenery, but also expressions on a character's face, describing their reactions. A literary story, by nature, needs plenty of poetic description. They thrive on them, and some are known for the way they describe something, not having a traditional plot, climax, or ending in many cases.

Additionally, a short story doesn't have a lot of time for long, detail descriptions, whereas in a novel you have more room for that sort of thing.

Audience - Young Adult, especially if you're focused on the early teens, generally wouldn't need Tolkien-like scene descriptions. I remember when I was reading Lord of the Rings to my two sons at bedtime. My youngest, about twelve at the time, complained, "He just took a whole paragraph to tell us, 'They got off their horses.'" I'm growing a book critic.

Meanwhile, adult or even later teens would appreciate more description than the bare bones, especially in a novel. I have one friend who relishes rich descriptions. She can "see" it in her mind. In my mind, what was said at the start becomes fuzzy as I read a lengthy detailed description, so I don't hold a whole picture in my mind. It is more like seeing a sliver of the scene and panning across it. By the time I'm at the end, I've forgotten what I saw at the beginning, and so the whole scene is foggy at best. Shorter descriptions make it easier for my mind to process and form a picture.

Point of View - Omniscient point of view will enable the author to go into lots of detail, much as Tolkien did. A limited third, first person, however, will by necessity mean you'll get less detail—if you stay in the point of view.

When I took driver's ed in high school, we watched a film and were told to notice as many things as we could. Now, this is with us trying to be observant. The film was from inside a car, driving down a road. At the end of it, we were asked a series of questions, like "what color was the car dealership sign." I caught some, missed many. So did a lot of people. When you're going through your normal daily routine, you notice even less.

Actually, from a first person point of view, or close third, you would rarely mention any scenery because we frequently don't pay attention to it. But that's one area where books aren't exactly like real life because you really need to tell the reader more than what the average person would notice. That said, in a close point of view, you'll stay more in it if you pick out specific descriptions. When you go into a more detailed description in such a point of view, you are actually moving out of that point of view and into a camera or omniscient narrator point of view. The good news is, if done right, the reader will rarely notice this. But if you overdo it, it can become jarring.

The circumstances - There are naturally times when your character would notice detail more, and your descriptions would reflect that. When I wrote a scene in my yet to be published book, where my protag first enters a virtual reality world, I have him noticing things in great detail. The idea is that he would be soaking this new experience in. He'd be studying his surroundings, so naturally the descriptions should reflect that level of attention.

Another key circumstance is what importance a place, person, or event has for the point of view character. The more important it is to them, the more description you'll want to give it. The more it plays into the story, the higher up the ladder of detail you'll want to use.

This is even true in omniscient point of views. While they can go to town on description, not being limited to one person's point of view, if you describe everything in the characters life in vivid detail, you're going to end up with a long book full of descriptions but little room left for plot or story. You'll bore your reader if you describe in detail every cup a character uses. Unless that information is vital to the story, you'll do more harm than good.

You'll want your description level to reflect what your character would notice at any given time, and what they notice should be important to them: what they like, what they would naturally notice, with the caveat that sometimes we as authors have to add in more than they would naturally notice to make the story work.

The Type of Description - Scenery and character descriptions have two different goals. Scenery you want to not only give the reader an idea of what environment your current scene is taking place, and describe that adequately enough that they can form a clear picture in their mind, but you also want to use it set a mood, sometimes even to foreshadow something. How much? Again, it goes back to what we've discussed so far. Who is the audience? What type of writing/story is this? How important is this place? How important is this scene (i.e., is it the climax, major plot point?) But finally it can depend on the author's style and preference as well.

Describing characters has a different goal. It doesn't hurt to know what color their hair and eyes are, how they're built, but there are two general rules to be aware of and to break them on purpose rather than accidentally.

One, the main reason to describe a person in the story is to add depth to that character, to highlight the traits that make the character more real, tell us their inner character as well as their outer looks. If a description doesn't do that in some fashion, then it is best to be left off. As an example, there's not much reason to tell us if the character is right handed or left, unless that fact either becomes important to the story later, or tells us something about that character. Emphasizing that a person in your story is left-handed could indicate the person doesn't go along with the crowd or looks at the world in a non-standard way. But to tell us that just to tell us that adds little to the character or the story.

Two, if your point of view is a close one, first or third, you want to avoid describing the point of view character. It is simply rare that such a character would ever do that. First, if you're in their "eyes," you are not going to see yourself very often. Second, if they do see themselves, say in a mirror, they are going to be so used to it that they won't notice in particular the color of their hair or eyes. When you brush your hair in the morning, do you think to yourself, "I swept the prickly brush through my deep, amber hair while my blue eyes stared back at me." No, you've seen and done this who knows how many hundreds of times. You're character isn't going to be noticing these things. Especially if he is a man.

And I guess I'm obligated to say that this point, that having a character describe themselves in a reflection will usually mark you as a beginner in most editor's eyes. Avoid doing that.

If traits of your character do need noticing, there are ways to get around this. One, have other people notice them. In Jill's book I reviewed, Achen had a "stray brand" on his back, left shoulder. He couldn't see it, but when a helper pulls his shirt off and reacts, you get the idea that there is something important on there. As it happens, this plays into the story later on, so it is important the reader be aware of this. By having this servant, and later Sir Gavin take notice of this, the reader is let in on its presence even though Achen can't see it and would generally not even think about it.

Another equally valid route is if your book has two points of view and they meet, they can describe each other in their points of view. Usually first time they met, as that's when they'd particularly notice various traits. If your story picks up after they've been together for a while, however, they aren't going to be thinking about the others looks unless you have a "special moment," like when the two stare into each others eyes. The point of view character is likely to notice the others eyes at that point.

I could probably dig up more, but those are the key points to consider. Probably the biggest mistake new writers make is describing events, places, or people in detail who aren't really that important to the story. If a description isn't either adding to the storyline, or setting the scene/mood of your story, then consider dropping it.

But in the end, this is one of those things writers will disagree on. Some like it thicker, others like it thinner. Since there are both kinds of readers out there, we're probably both safe. What guides do you use to decide how much description to lay on the reader?

Check out these other sites participating in the CSFF Blog Tour:








Brandon Barr
Keanan Brand
Gina Burgess
Beckie Burnham
Melissa Carswell
Valerie Comer
Karri Compton
Amy Cruson
CSFF Blog Tour
Stacey Dale
D. G. D. Davidson
Jeff Draper
Emmalyn Edwards
April Erwin
Sarah Flanagan
Andrea Graham
Tori Greene
Ryan Heart
Joleen Howell
Becky Jesse
Cris Jesse
Jason Joyner
Julie
Carol Keen
Krystine Kercher
Dawn King
Leighton
Rebecca LuElla Miller
New Authors Fellowship
John W. Otte
Crista Richey
Chawna Schroeder
Andrea Schultz
James Somers
Rachel Starr Thomson
Steve Trower
Fred Warren
Dona Watson
Phyllis Wheeler
KM Wilsher