Tishta the Crystal Orb: Beta Readers – Round Two

After finishing the last edit of “Tishta the Crystal Orb,” I drew two of the six maps for the book, figured out how to include them in Scrivener, and sent the ARC (Advanced Review Copy) out to a couple of Beta Readers. I am so excited, I can barely contain myself.

For the maps, I scanned my pencil sketches into .jpg files. Using PhotoShop, I added them as the lowest layer, then drew over them—with my finger on my trackpad—and added text labels, etc., then removed the original layer. It was tedious and the maps are fairly crude, but they definitely show the landscape and the routes my travelers take.

Adding the drawings to Scrivener was a learning process. I had to figure out how to scale them up to fit the page, then what to do to exclude the title of the page. I ran into an issue when I started updating the .epub files on iBooks on my iPhone (it worked fine on my Mac). It remembered positions from the previous file, and it really messed with the formatting of the pages. Now I know to always name the file something different, so I append versions, e.g., Tishta the Crystal Orb 2.1.epub. I did not have this issue with Kindle, but I think it is a good practice, regardless.

Next up is to finish the other four maps—a friend lent me a drawing tablet to attach to my laptop, which is making things easier—then create updated book versions to send to my readers. I also need to contact a few of the people who did not respond to my initial email to see if they are not interested or maybe missed the email.

I have been trying—only somewhat successfully—to hold off on doing any more editing until after I take the class on creating an audiobook on the 17th (see previous blog post for details). I am really ready to record the scenes again. It is difficult to listen to the current version since I can hear things that should change, and I am not certain if I have already changed them—I did a major edit since they were last recorded.

The value of recording as an editing tool was reinforced over the weekend when I recorded a scene before reading it at one of my reading groups on Sunday. I do this to ensure I can read the whole scene within the allotted five minutes of open mic. There were several places in the short scene where the words caught my ear as not quite right. I made the changes before I read it to my group.

I found a line editor who I will possibly hire. I need to figure out at what point it will make sense for her to read it. Probably not until after I make edits based on Beta Reader feedback, and perhaps not until after I record the book again. All these things are trial and error. Next time, I will know more. But that is life, in general.

Thanks for your words of encouragement and advice. I appreciate it. I should be editing. More later.

Copyright ©2014-18 Ramona Ridgewell. All rights reserved.


Tishta the Crystal Orb: Outline Update and Full Edit Pass

Damn, it’s been a month. I made a second pass through the outline of “Tishta the Crystal Orb” to add the point of view (POV) for each scene. So, I read the whole book again. This time, I carefully edited each scene. On the last pass, I started out thinking I should simply outline, but started editing more and more as I went through the book. That was apparent on the current pass—I made many more changes in the first half than the second.

While my focus was on finding scenes to remove that were not moving the story forward—and I did do that—I also changed a lot of text to make the verbs active. For example, “was sitting” became “sat.” An added bonus was this also reduced the word count, by onesies. Other similar edits included looking critically at prepositional phrases to ensure they were required and not just eye candy.

Adding a focus on POV helped me keep the story more in the narrator’s voice and out of people’s heads. I still go there, but more judiciously. Again, this reduced the word count as “Malcan saw Gillan draw her sword” became “Gillan drew her sword.”

On this pass, the word count dropped from 164K words to 155K. Not too bad, although my goal was, and still is, 150K. When I started editing the second draft of Tishta, the word count was 187K, so about a 20% drop. I am happy about that.

My next step will be to engage with my second set of beta readers to see who will have time over the next month to read the book. Of course, I will ask them to report any plot holes or anything that feels inauthentic, but my primary ask will be to let me know where the story feels slow and what, if anything, they think I could remove without harming the story.

On March 17, I will be taking a Hugo House course presented by Brian Callanan, with help from Wendy Terrien, “Understanding Audiobooks: A New Chapter for Writers.” If you are from the Seattle area, you might recognize Brian’s name—he has worked at Q13Fox. He is a voice over artist and can be found on Facebook at Brian Callanan Voice Over & Audiobook Narration. I am really looking forward to this class since I fully intend to record Tishta myself. If you follow my blog, you know that I record every scene. I find hearing the words is one of my best editing tools, and, I enjoy listening to my story.

When my beta readers have given their feedback, and I have recorded and listened to the story, I will make one last edit pass through the book. Then, I will be ready to share it with everyone.

I am excited to be so close to publishing. I met with an artist this week, Kaitlin Robinson, who has agreed to do the cover for me. She is the sister of a good friend, and I like that—keeping it in the family.

On a recent visit to Third Place Books, I discovered they have a small publishing press. I need to check it out to see if it will be a good option for me to create a physical book. I will have to pick the brains of some of my author friends to figure out the best approach to digital distribution. I still would like to create my own distribution page to go along with my soon-to-be-created author page. That would give me the added benefit of having something new and cool on my CV for my “real” profession, which is software development. I sometimes wish there were about six more hours in a day.

That about sums it up. I will try to post more regularly now. Let me know if you have any comments or advice for someone at this point in their first book. I would hate to miss something that would seem obvious to an author who has already been here.

Copyright ©2014-18 Ramona Ridgewell. All rights reserved.

Tishta the Crystal Orb: Outline Finished

I am ecstatic. I finished the outline of “Tishta the Crystal Orb” today. After cruising through “Part 4: Colmaria” in four days, “Part 5: Mondar” was more of a slog—it took twelve. Granted, at 42,402 words it is 65% longer than Part 4.

Even though, as I have said in past posts, this pass through the book was meant to simply provide an outline, I was hard-pressed not to edit along the way. As I noted each beat in each scene—a technique author Anaea Lay suggested—it seemed prudent to trim the ones I felt were extraneous, especially this far into the book, where I feel more confident that whole scenes are unlikely to be cut. I also could not refrain from rewording, or removing words, where appropriate. At the same time, I ended up adding bits and pieces, where I felt the story would be better with the new words—there is more of this to come after I read through my notes. In the end, I trimmed the word count by 9%, down from 46,521.

While the page count dropped a bit, and the scene count stayed the same, I ended up splitting a long chapter into two, making the break at a tense moment in the story, to add to the tension. This was on the advice of author Elizabeth Guizzetti, after she graciously offered to read my second draft, and provide feedback and comments. This was a good call on her part. I like how it broke up the flow.

My next work will be to analyze the outline, looking for beats or whole scenes that do not move the story forward. Because I know this will mostly affect the first half of the book, I held back earlier on making the copious edits I allowed myself in Part 5. After taking a quick glance at the current revision in .epub format, I could not help myself—I immediately made some edits. It is interesting how I notice things in this format that do not pop out when I read the same thing in Scrivener. It is going to take discipline to finish the analysis before diving into edits like these—that is work for the next phase.

I expect that cutting scenes will be the most challenging thing I have experienced, so far. I have heard stories of authors crying over favorite scenes that dropped to the cutting room floor. I am bracing myself for this inevitability, but I owe it to my readers to provide them with a properly paced book. I am beginning to understand how it can take years to publish a book, and how some books never are. I love my stories. I want to share them. I will do this.

Copyright ©2014-18 Ramona Ridgewell. All rights reserved.

Tishta the Crystal Orb: Part 4 Is Outlined

Only four days since I finished outlining Part 3 of “Tishta the Crystal Orb,” I have outlined “Part 4: Colmaria.” Jury duty has a nice way of providing distraction-free time.

The word count went from 27,175 to 25,465, and the number of pages dropped from 90 to 74. This edit is not meant to reduce these counts, but to outline the scenes, and their beats, in a spreadsheet. Beats are each action or feeling that happens in a scene. Since I am reading each scene fairly thoroughly to identify the beats, I have edited to remove words, or even beats, as I go. That accounts for the drop in words.

In a previous edit, I broke out actions very discreetly. This was useful in identifying what I later learned are called beats. Although very insightful, it left the manuscript with each paragraph containing the actions of a single character. I went so far as to separate the dialog from any sentences around them. This resulted in a lot of one-sentence paragraphs. The second draft—the one I sent to a group of Beta readers—was structured this way, and much longer than it needed to be, as a result. As I have gone through the book since then, I have created more complex paragraphs that include all thoughts, dialog and actions around a single character-initiated action. The dialog in any given paragraph is all spoken by the same character. The number of pages has shrunk as a result, which is good. I think I am happy with this methodology, but need to wait until I next record the book to see how it sounds.

After I finish outlining, I hope to figure out which scenes can be reduced or eliminated, to pick up the pacing—especially in the first half—as well as to reduce the overall size of the book. At that point, I can realign the moon—I have at least two scenes that depend on it being full—and draw the final version of the maps. I tentatively plan to do one more full edit, looking for extraneous items on my ever-growing list of words and phrases that I “should not use,” or, at most, should use judiciously. I will share that list in another blog.

I am totally stoked about outlining “Part 5: Mondar.” It is where a lot of the action takes place on the way to the grand finale. I made some headway this morning, but then, duty called—I was included in a jury panel, which was my hope during this week of civil servitude. I am excited to see more of the legal process in action and will be more than happy to sit on the jury if I am selected. Tomorrow morning, I will find out. For now, I should get to bed. The six o’clock alarm will sound long before I am ready.

Copyright ©2014-18 Ramona Ridgewell. All rights reserved.

Lessons from the Fledgling Author: Editing Is Hard Work

I am fairly certain I will spend as much time editing “Tishta the Crystal Orb” as writing it. Granted, the editing involves some writing and re-writing, but, damn, the rest of it is very time-consuming. I know part of the reason it is taking so long is that I am a novice. I learn from my experiences, and I hope, that by sharing, you can avoid some of the mistakes I have made along the way—mistake is too a harsh word—and make your editing more efficient.

While attending writing panels at conferences over the last few years, I have heard many views on best practices. Some writers advocate starting with an outline, while others write by the seat of their pants—“pantsers” was a word I learned. The latter style seemed to apply to me, so I did not worry about outlines.

When I started writing, it was because a story was demanding to get out. So, I wrote it. The words flowed freely from my brain through my fingers into my computer. It was very stimulating. All my free time was taken by this single endeavor. I would sometimes write until two or three in the morning, so I would not lose the story. I knew, all along, that I was writing an epic fantasy. I expected to write a trilogy. Our brains are conditioned to this—beginning, middle, conclusion. Star Wars is the prime example.

When I lifted my pen, so to speak, I realized the first book was an epic unto itself. I did not note the word count, but when Scrivener told me it was seven hundred fifty pages—and I had a major section in the middle to complete—I knew I had a problem. The missing part was meant to be that failure of the hero on his way to figuring out how to win. It seemed like an obvious place to rip the first book asunder. And, that is what I did. Then, I had a tetralogy.

In finishing the “new” first book, which is titled, “Tishta the Crystal Orb,” I was cautious to keep it more terse. I succeeded, and the first draft was around eighty-seven thousand words. This seemed appropriate for a first-time author. A fellow writer, Anne Bean, who has done editing, agreed to go through the book. It was a very exciting time for me.

While Anne read “Tishta,” I felt an intense desire to know more about Coltan, my vampire and main character. Somewhere along the line, I wrote bits of his back story, including scenes from childhood and adulthood before he was turned into a vampire. It gave me a good feel for what kind of man he was, and some of the things he had gone through. I had also written the longer story of how he met Criften and was “tamed” by the wizard. I knew some of the pieces of his life between his beginnings with Criften and where the story starts in “Tishta.” I wanted more. I needed to know the story of Coltan dealing with his distress at killing a lover—during a passionate sexual encounter with her, his bloodlust overcame him.

What began as a simple backstory, blossomed into a novella of around fifty-thousand words. A month later, I had five books. Tentatively titled “How to Tame a Vampire,” this book follows Coltan on his journey to Soldur, to meet the wizard, Eido, who specializes in swordsmanship, as well as psychology. In it, Eido guides him as he learns to separate his desire for blood from his sexual passion. In this story, I learned to write explicit sex scenes.

During the first year, when I was writing the originally planned first book, “Into the Wolf Dream”—which is the title of the now second book—I wrote major parts of the final book, “The Golden Key,” and parts of the middle book, “From the Detritus of Evil.” Because so much goes on in so many places—which all need to align for the Coming Battle at the end of the last book—I fill in pieces of these future books as I write. I have easily written over a million words for the complete story.

Because the whole story is so long, authors I know have been suggesting serializing it—breaking it into smaller pieces so I can publish more frequently. This may be the way to go with self-publishing, but right now, I will stay focused on publishing “Tishta” as full-fledged novel.

After Anne provided feedback that the story was fairly solid, but the characters, places and time flow needed elaboration, I let myself go. After nine months, “Tishta” grew to one hundred eighty-seven thousand words—more than double. I edited it down to one hundred seventy-two thousand.

In the fall of 2017, I called the second draft of “Tishta” complete. I gleefully sent it to several beta readers. The benefit I am receiving from their feedback is immeasurable, and it gives me the confidence to continue. I know the book is too long, and the pacing is too slow in places, especially in the first third, or maybe half. I was lucky to have a published author, Elizabeth Guizzetti, offer to read the story. In a flash—literally, in just over a week—she got back to me with feedback and inline comments. Whoot! Her feedback and criticisms helped me make some decisions about characters and plot. I love the support my local Seattle writing community offers me.

After taking a month to explore editing methods—to help me decide what to cut and where to cut it—I began adding a goal, a conflict summary, and an outcome, to each of my scenes. This was a suggestion from a writing channel on YouTube. It gave me fuel for thought, but did nothing to give me insight into my editing. This ended up being a waste of time.

The idea to document what each scene involves was encouraged by another published writer in my Seattle network, Anaea Lay. She suggested outlining the scenes in a spreadsheet, including a list of each beat—or action—as well as a list of characters and whatever other notes seem appropriate. At the beginning of December, I began using a spreadsheet to outline. It has been a month, and I have gone through the first three parts—as of today. This approach seems like a good one, and I am planning to outline the whole book this way—two more parts to go.

Beside the beats, I am keeping track of the word counts, which nights transpire, who the characters are, and notes about what, of importance, happens. Several things have come out this already. I have become more conscious of higher level story beats, that I hope will help me figure out which scenes are not holding their weight. I also notice who is missing from a scene, or a series of scenes, and think about how or if they should be included. I already kept track of the nights as a means of understanding distances and knowing the phase of the moon. Now, I can see how much time passes not only in each scene, but also in each chapter and part. I hopes this helps identify places where I can cut days out.

I started out thinking I should simply document what was currently written, with the intent of coming back on a later edit pass—after I know more—to decide how to trim things. As I went, I found I was critically reading each beat—so basically, each paragraph—anyway, and started to feel I was wasting time leaving things that I could see needed editing. I might regret this decision later, but I have been reviewing and changing things that I notice. The word count has fallen by about five percent. And, my writing style is continuing to evolve in the process. Since I did not start out editing as I went, the earlier in the book, the less editing took place. The ending of my book always feels more polished than the beginning.

So, that is what I have been up to since I last updated you all. I might not get back here again until I finish outlining the final two parts. I will compare what that tells me with a map I already drew—the map points out that too much travel takes place in the beginning, which was already a red flag—to find the places I should consider trimming and cutting.

Although this has been a long, and sometimes grueling, process, I find a certain satisfaction in editing. Once I get the process down, I believe the next books will be easier and quicker to finish. I will be using the spreadsheet to outline much sooner in the process. It’s all good. I’m learning.

Copyright ©2014-18 Ramona Ridgewell. All rights reserved.

Lessons from the Fledgling Author: There Are Places I Remember

A question came up in one of my Facebook writers’ groups today—is it all right to write about a place you have never visited?

It is certainly best to write what you know, but that is not always possible. In your research of a place, do not forget to understand its geography, what plants and animals live there, and what the climate is like, especially during the time your story is set there. Investigate the local cuisines and dress and other cultural aspects. Then, create a character that is that place (and, now I realize, I should do this). Describe if it is hot or cold, dry or muggy, dusty or moldy, noisy or quiet; how it smells; what colors it is; if the buildings or rocks or whatever are rough or smooth, spiky or rounded. If it is very hot, describe how the air feels entering a character’s lungs, or how their lips dry and crack. If it is very cold, describe how their toes get numb and, the longer they are outside, how the cold creeps across their feet and up their legs. Those are the showing things you can use to describe a place you have never been. It helps if you are describing something you are at least familiar with, even if you have never been to the exact place.

If you have never been in snow, felt it touch the skin on your cheeks, made a snowman, or run outside in your bare feet just to see if you could make it to the fence and back, then you will be hard-pressed to be able to describe it. If you have never tried to sleep when the temperature is 90°F, the humidity is 98%, there is not a breath of air moving, and the cicadas are so loud you can’t hear anything else, it would be hard to pretend you know what that feels like. Your readers who have experienced these things, they will know.

Copyright ©2014-17 Ramona Ridgewell. All rights reserved.

Lessons from the Fledgling Author: Too Much Hair

I keep reading that I should limit—even severely—the descriptions of my characters. Yesterday, I read a 2001 article in The New York Times by the late author, Elmore Leonard, titled “Easy on the Adverbs, Exclamation Points and Especially Hooptedoodle.” It was from their WRITERS ON WRITING series. Point 8 said, “Avoid detailed descriptions of characters.” It went on to say, “Which Steinbeck covered. In Ernest Hemingway’s ‘Hills Like White Elephants’ what do the ‘American and the girl with him’ look like? ‘She had taken off her hat and put it on the table.’ That’s the only reference to a physical description in the story, and yet we see the couple and know them by their tones of voice, with not one adverb in sight.” I would guess, you might envision these characters as white Americans, as I did.

I understand this concept. It allows the reader to become part of the creation of the story—to become vested in the characters. I think it might be outdated. When we let readers create their own images of our characters, they will more than likely view them as white, and probably with light hair and blue eyes. In American media, we are completely conditioned to do so—even consumers who are not white.

My characters are predominantly brown. They come from mixed places and cultures—much like our own America. I feel it is important to make it clear that my protagonist would not be played by one of the Chris’s—Hemsworth, Evans, Pine, Pratt. I would choose someone like Jeffrey Bowyer-Chapman. I do not know how to do this without describing him in vivid detail.

Screen Shot 2017-11-17 at 14.48.07

Jeffrey Bowyer-Chapman – Photo: Paste Magazine

In the first scene of “Tishta the Crystal Orb,” Coltan arrives.

“He was a large, muscular man, about the same size as Malcan—but that is where the similarity stopped. His dark walnut hair was neatly cut to just above his shoulders. As he turned, one wavy lock fell over his brow, above expressionless brown eyes. His hand ran up over his head, integrating it into the rest of his hair. He wore a well-tailored black riding coat, and black boots that came halfway up his calves—he looked like a gentleman, out for an evening ride.”

I attempted to do a couple of things here—and maybe it is too descriptive. He is a big guy. Even though he is traveling, he keeps himself neat and clean. But, I also described his wavy, walnut-colored hair and brown eyes. Later, I describe his skin.

An issue one of my early readers had was that I described everyone’s hair in the first two chapters. But that is where I introduced the majority of my main characters, and there are a lot of them—eleven, at least. That was a lot of hair. I have since removed some of those descriptions and put them in later chapters—I still think it is important to note that it is not blond and straight. Well, actually, one of them is currently golden-haired, but I need to make her darker to fit in with the place she is from, as well as make her physically more similar to her cousin, who is another one of travelers.

Even Malcan and Brant, the two fairest among the group—with blue eyes—have dark hair. Brant’s is black. Malcan’s is dark auburn.

My lead warrior, Gillan, and her side-kick lover, Toran, are from a place where everyone is what we would call black. Their skin is very dark, their eyes are nearly black, and Gillan’s black hair is softly curled. How can I not describe at least some of that the first couple of times they are introduced?

“Shortly after the sun passed its zenith, Gillan slowed her horse while she removed the cord that bound her black hair. She shook out the curls before retying it.”

In the same scene, I described the boy, Kano. While he is not black, he is… well, I’ll let you read it.

“She was surprised to find a young boy, no more than eight or nine, sitting in a ray of sun.

His clothing, skin, and even his long, straight hair, so nearly matched the color of the russet and tan stones around him, he almost blended in with them. Laying beside him were a quiver of arrows, a bow and a small pack.”

Again, I think it is very important to describe him in this much detail when he is introduced, and not let the reader envision him as a white boy.

Ever since I first pictured my very large warrior, Toran, I have seen Isaiah Mustafa in my mind. If I was casting Tishta as a film, Mustafa would probably be my first choice, although, he is a little old to play my 30-year-old warrior. One night, a couple of years ago, I had the pleasure of eating dinner with Mustafa. Toran embodies a lot of Isaiah—big, handsome, beautiful smile, polite, deep booming voice (not the Old Spice voice).


Isaiah Mustafa with Michael Rosenbaum at 2015 Echoes of Hope Celebrity Shootout Hockey Game – Photo: Ramona Ridgewell

Interestingly, in all of the early descriptions of Toran, I just discovered I do not describe him beyond how large he is. Now, I wonder if my readers assume he is as dark as Gillan, since they are a couple. And, I wonder if my transposition of Mustafa onto my character made it so I found no need to describe him. Writing about things like this always seem to lead me to some new revelation. I shall undertake an investigation of all descriptions of Toran.

I am interested to know how other writers overcome the assumption of their readers that their characters are white. Let me know in the comments.

Copyright ©2014-17 Ramona Ridgewell. All rights reserved.

Lessons from the Fledgling Author: Beginning of the End

It has been two great weeks. I am up to nine Beta Readers! Yay! None of them have finished yet, but I am really looking forward to their comments, insights and criticisms.

Two weekends ago, I had the good fortune to be invited by Joe Follansbee to his “Carbon Run” book launch. I had never attended one before, so it was good to see what kinds of things one would expect from such a party. I will be presenting one soon. There were several published authors in attendance. While I did not meet everyone, I was introduced to K C Blackbyrn who recently published her first novel, “Stirring Power.” We had a great discussion about editing, editing, editing.

The best part of the afternoon was reconnecting with Elizabeth Guizzetti, author of “The War Ender’s Apprentice” (new on Kindle), “The Grove,” “Other Systems,” “The Light Side of the Moon,” and “Famine Lands: The carp’s eye.” I know her from Two Hour Transport, where she occasionally reads, and many writing panels she has been on at various conferences around Seattle. Much to my surprise, she offered to read Tishta and provide critical feedback. She followed through during the week. This week, I have been reviewing great feedback to incorporate into the book. I cannot thank her enough.

Some of the feedback from Elizabeth confirmed what I already suspected: the beginning moves too slowly, indicating there are scenes that should be cut; I describe where people are looking far too often; I overuse certain words, like just, up, down, and very, to name a few—for some of the ones Elizabeth pointed out, I have already made edits to cut back on them, but apparently, even what is left is overdone.

More importantly, she pointed out how obvious it was that I did not invest myself in the character who dies. I think I did not want to deal with the grief I knew would come if I let myself love her. One of my new tasks is to write her backstory, and learn to love her. Then, I will be prepared to rewrite her story in Tishta.

Elizabeth also helped me see where my story falls into stereotypical female responses under stress. I have some changes in mind to fix that for some of the things my lead warrior, Gillan, does to respond to her grief. I think this will greatly improve the story and the character.

In the mean time, two more beta readers joined my group. Maybe at least a few of them read the book and give me some feedback. I am hoping to garner more insight into the story and the characters. I gave my readers a deadline of Thanksgiving to return feedback. My plan is still to publish by the  end of the year. It will be a tight schedule to review the feedback and re-edit the book in a month, but I will give it my best shot.

I think this last month away from the book has been a good thing. Hopefully, I will read it with fresh eyes when I again dive into editing. It has been hard not to do this, especially after receiving the feedback from Elizabeth, but I think it is important.

I have been researching how to self edit and publish online. One video by Ellen Brock suggested that, even if you do not write from an outline, it is a good practice to outline your story. She says it will assist in finding the scenes, or even chapters, that do not move the story forward. For every scene, she looks for the Goal, the Conflict and the Outcome. Every scene. I am going through my book to create this now. Fortunately, Scrivener has a synopsis built right into the editor—and they show up as cards in the Corkboard view—so, I am writing these notes in the synopses. I am already finding a lot of scenes where I cannot define the Conflict. I think this technique will be invaluable in discovering the scenes that can be cut, especially from Parts One and Two.

I am really looking forward to this next edit. In the meantime, I have gone through the book to document how far the group travels. My first shot at drawing the world—beyond the rough sketches I needed to try to keep track of them—has shown me places where the world is either too big or too small. I will make adjustments in the story to accommodate a more perfect world. The other part of drawing my world is ensuring the places they do not visit fit in to my vision for the rest of the complete story arc, which is spread out over at least four more books.

In completing this first book, I have been forced to include many of the elements I will need from this story to support the following stories. It has made writing this book take longer, but I believe it will make the entire story arc more consistent, and the following books easier to write.

I should return to doing my book things now.

Copyright ©2014-17 Ramona Ridgewell. All rights reserved.

Lessons from the Fledgling Author: Making Notes with iBook

I wrote about making and exporting Notes from a Kindle (on a Mac). In this blog, I will explain how to do that on an iBook. Interestingly, this is far more straightforward on my iPhone than on my Mac—just the opposite problem from the Kindle.

First, I will talk about the iPhone, since it is the easiest to use. Download the .ePub file. I think it automatically opens into iBooks. You’ll have to scroll back to see the title page, copyright, beta readers’ notes and, dedication. Otherwise, just start reading. When you find something to comment about, select the text. Above the selected text, a menu should appear with “Copy,” “Highlight,” “Note,” and and arrow to the right. Select “Note.” Then, type in the comment.

Click “Done,” at the top right to get back to the book. Keep reading. Add another comment. If you just drag you finger over a block of text, it automatically makes it into a Highlight to which you can add your comment. Sorry, the top-level menus don’t get captured in the screenshots on iPhone.

When you are ready to export the Notebook, click the Menu icon at the top left.

Switch from “Contents” to “Notes.”

Click the Upload icon at top right. Select “Edit Notes.”Then, “Select All” at the bottom left of the page. Then, click “Share,” which is at the bottom in the middle. This will pop up the option of where to share it. If you choose email, it puts the notes into email.

As you can see from the email I received (at the right, above), I did not get much context on where the comment occurred. Be sure to include enough of the text to make it easy for me to find it.It would also be nice to know the Chapter and Scene.

For exporting Notes on iBook on a Mac, the only method I have been able to find—so far—is covered on this YouTube video. The gist is that, when you are ready to export the comments: open the Notes panel by clicking the third icon in the top menu; expand all of the chapters to see all of the comments; select all the comments and copy; paste into email. It’s pretty ugly, but it works. Let me know if you find a better way to do this.

Copyright ©2014-17 Ramona Ridgewell. All rights reserved.

Lessons from the Fledgling Author: Making Notes with Kindle

My writer’s journey has led me to figuring out how to get feedback on my first novel, “Tishta the Crystal Orb,” prior to its publication. Over the course of the last year, whenever I talked to people about the book, I asked them if they would become Beta Readers. I ended up with a list of around two dozen friends and acquaintances, as well as a few strangers. Over the weekend, I felt ready to share “Tishta” with other people, so sent out an email explaining what I was requesting of them. To my happy surprise, seven of them have agreed and taken possession of a beta copy of the ebook and provide me their thoughts about it.

One of the complications is how to communicate the feedback. I knew that in a Word document, you could take notes, embedded in the text. This is how my editor, Anne Bean, provided feedback on the first draft of “Tishta.” Recently, I discovered you can make notes in both iBooks and Kindle. This blog tells how to do it for Kindle on a Mac. A following blog will include iBooks instructions.

First, download the .mobi file. If you double-click it, Kindle will open into the book. This can be pretty slow, so be patient.

Screen Shot 2017-10-12 at 12.50.34

You’ll have to scroll back to see the title page, copyright, beta readers’ notes and, dedication. Otherwise, just start reading. When you find something to comment about, click the “notes” icon—at the bottom of the menu on the left side.

Screen Shot 2017-10-12 at 12.58.29

That should open the Notebook panel.

Screen Shot 2017-10-12 at 12.58.59

Next, highlight the text you want to attach a comment to, and click “Add Note.”

Screen Shot 2017-10-12 at 12.59.43

This should bring up a pop-up dialog where you can type the comment.

Screen Shot 2017-10-12 at 13.01.40

Click “Save.” The highlighted text and the comment should show up in the Notebook.

Screen Shot 2017-10-12 at 13.01.51

Keep reading. Find another place to note.

Screen Shot 2017-10-12 at 13.04.16

Click save. It will show up beneath the first comment in the Notebook.

Screen Shot 2017-10-12 at 13.04.24

One note about text selection: Always select more than one word, otherwise, there is no highlight to go with the comment. It will be easier for me to match up the comment with the text if I have some context to go on.

Screen Shot 2017-10-12 at 14.59.02

Screen Shot 2017-10-12 at 14.59.29

When you are ready to export the Notebook, click the upload icon at the top of the Notebook panel. Click OK on the warning. Then save it somewhere that you can find it.

Screen Shot 2017-10-12 at 15.02.14

Screen Shot 2017-10-12 at 15.02.57

This generates a .html file. Here’s what it looks like.

Screen Shot 2017-10-12 at 15.03.34

I haven’t figured out how to import the .html yet so I can apply it to my own copy of Tishta, but I think this will be a workable option.

There is definitely a way to make notes on Apple devices—specifically, my iPhone—that is similar to the steps above. It appears to be complicated to extract/export the notes from an Apple device. It might be possible to sync up to your Amazon account, but that might not work for a local copy of a book. I don’t see the export icon that some of the how-to blogs talk about. One talked about a new email option, but I can’t find that, either. If someone figures this out, let me know and I’ll update this blog.

Copyright ©2014-17 Ramona Ridgewell. All rights reserved.