Showing posts with label formating. Show all posts
Showing posts with label formating. Show all posts

Tuesday, August 16, 2016

Word Perfection

No one is perfect.  Well, except Nadia Comaneci, and Torvill and Dean.

That doesn't mean we can't or shouldn't strive for perfection.

I take a great deal of pride in my grammar, spelling, and proofreading skills.  I know that mine are above average, but I also know that the results of refining those skills are attainable by nearly every writer who dreams of uploading a manuscript to Amazon. 


I finished the actual writing of The Looking-Glass Portrait on 11 July 2016.  Because it was written using Word Perfect, I had to convert the document to Microsoft Word before I could upload it.  There are certain conventions of the two softwares that are not 100% compatible, so I had to go through the entire manuscript and make manual corrections to things like em and en dashes, tabs and ellipses, double breaks and so on. This also gave me the opportunity to look in both versions for marked spelling errors and fix them. 

Spell check tools are wonderful.  They won't catch everything, but they catch a lot.  Anyone who doesn't take advantage of them is just plain foolish.  I've seen too many author-published works on Amazon that have clearly never been run through even the most rudimentary spell-checking program.  This is unforgivable.

After putting my MSWord document through the conversion to HTML and then to mobi, I uploaded it to Kindle Direct Publishing on 18 July.  Yes, just one week.  No one else had read it.  No one else had proofread it.  No one else had edited it.  I knew I was taking a huge risk that I might have missed something major, but I was willing to take that risk and trust at least to my own proofreading skills.

The uploading process contains its own spell check application.  I used it, too, because you never know what the other programs might have missed.  And they had in fact missed one typo that I was able to fix before uploading.  I hit the "publish" button.



By Word Perfect's count, the book is something over 138,000 words long.  After a few readers got back to me, we had identified a grand total of three -- three -- errors that escaped my eagle eyes:  a missing space between two words, a wrong word, and a missing word.  All were easily fixed so the corrected document can be uploaded to Amazon.

Am I bragging?  Yes, I am!  But I'm also saying that this can be done by anyone who is willing to learn the skills or learn to rely on others who have the skills.  Your readers should be able to sit down with your book and read it, not correct it.  Are three errors acceptable?  Well, not by me!  Would I throw a book against a wall for three errors in 400 pages?  No, of course not.  But I wouldn't read past the first page if I found three errors on it.

It's not enough to put your heart and soul, your blood, sweat, and tears into you book.  You have to put your skill into it, too.  Language is the absolutely essential tool you have with which to build your literary world, and if you don't learn to use it with consummate skill, you probably won't be able to tell a story people will be willing to pay good money for.


Thursday, February 12, 2015

Separation of words and self

The past several weeks have been rather, shall we say, challenging for me, which is why I haven't kept this blog up quite as regularly as I would have liked.  Two separate writing projects have demanded my time and concentration, as well as other aspects of real life.  Right now, however, I am facing the prospect of about a week tending a dog recuperating from surgery, so I'll probably have a lot of time at the desk and computer to catch up on some of the blogging.

One of the issues that's been brought home to me in some rather startling ways is this whole issue of writers wailing that their books are their babies.  They seem to use this claim as a justification for both outrage over negative book reviews and outright attacks (usually verbal rather than physical) on the reviewers. 

This is not a new phenomenon.  Writers have been dissing critics just about as long as there have been writers and critics.  My own experience goes back just around 30 years to my early days in Romance Writers of America and judging RWA contest entries.  In face-to-face critique groups and online groups, along with one-on-one evaluations, responses to criticism ranged from "You're right; I need to fix that" to "It's my book and I'll write it the way I want to!  Who are you to tell me how to write my book?"

After this more recent brouhaha over critical reviews which escalated to the point of reviewers receiving death threats, I wondered what is it that makes some writers react to criticism of their writing with such intensely personal outrage.  The reviewers don't know the writers; all they're doing is commenting on their reaction to the book.  And yet the writers take it so very personally.  Why?

I'm not sure why I happened to think of my old writing buddy EK last night, but I did, and I began to see a connection between her reaction to criticism 20 years ago and this current wave of battered egos.

EK was in her early 60s when I met her, a delightful, cheerful woman with an infectious laugh and a constant smile.  Nothing about her demeanor suggested she had been through some very, very hard times.  Her first husband had deserted her with two small children; she had at one point lived with the children in the basement of an abandoned church.  Her second husband was abusive, and in and out of jail for various not-so-petty crimes.  After two more children she divorced him, but he hounded her for years and years afterward.  He broke into her home, stole from her, made so much trouble that she was evicted from several apartments.  The problems with him only stopped when he beat her so badly -- because she didn't have any cash in her home for him to steal -- that she ended up in the hospital and he ended up in jail for a much longer stretch.

She had lived in or near poverty most of her life, unable to hold a job very long because of the issues in her personal life.  One child died of AIDS in the early days of the epidemic; another disappeared into the streets.  There had been other, serious problems, the kind none of us wants to have even one of but EK had several.

Two other writers and I had formed a critique group, and when EK asked to join we welcomed her.  At our first meeting she described her work-in-progress as a contemporary romance featuring a high school math teacher recovering from a bitter divorce and a firefighter who had just lost his young wife to cancer.  Given that this was the late 1980s, EK's characters were way ahead of their time in terms of the contemporary romance market.  The rest of us warned her about this, but she insisted this was the story she wanted to write, and these were the characters she wanted to write about.  Okay, fine.

The book began with a Prologue that provided almost all the backstory for both characters in a classic "Write Chapter 1, write Chapter 2, throw away Chapter 1" fashion.  EK politely accepted our suggestions that she weave backstory into the narrative, but continued to insist it was her story and she would tell it her way. 

At our next meeting, we critiqued her Chapter 1 (which was effectively her second chapter), which served to introduce the firefighter hero character. Though it was competently written for the most part, we three readers found some continuity and consistency flaws and a few other mistakes.  EK graciously and sometimes self-deprecatingly agreed with almost all of our assessments and said she would fix the errors.  My personal feeling was that she had a workable story in process, and if she continued to accept advice as well as she had, she would probably end up incorporating her prologue's info-dumpy contents into the story and ditching the Prologue to produce a viable book manuscript.

Our third meeting should have brought us to Chapter 2, but instead EK brought her revised Chapter 1.  She had reworked the sections where we had found problems, and she had made some other revisions and additions.  The new material revealed some other errors and weaknesses; she didn't argue with our comments and agreed these things needed to be fixed.  We specifically told her to let them go for the time being and bring us the next chapter.

She didn't.  She brought yet another revision of Chapter 1.  When we asked her why she hadn't brought the next chapter, she explained that she hadn't written it yet.  "I have to have this chapter absolutely perfect," she said, "before I go on.  This character is my hero, my hero, and to tell the truth I'm reluctant to share him even with the other main character in the story."

At the time, we all kind of laughed and teased her about falling in love with her own fictional creation, but as a few more meetings went by, she brought only the first few pages of Chapter 2 along with more revisions, more additions to Chapter 1.  It became clear that EK really had fallen in love with this fictional firefighter, and she wasn't about to share him.

For a variety of reasons that had nothing to do with EK and her book boyfriend, the critique group dissolved after about five months.  I stayed in contact with both EK and one of the other members for a long time afterward, long enough to learn that EK never did write any more on her book.  The other writer, who went on to be traditionally published, and I agreed that EK really wasn't writing for publication.  She was writing to create the kind of man and the kind of romance she had never had in real life. 

We further agreed that there was nothing wrong with this.  If EK had been pushed to finish her book, if she had found a publisher for it, she would have had to share her hero; and sharing him would have broken her heart.  She wasn't writing for readers, she was writing for herself. 

In at least one of the recent explosions of writer over-reaction to negative reviews, the writer had made it abundantly clear that she was writing the kind of story she loved.  As in EK's case, there's nothing wrong with that. 

What seems to be more and more apparent in each of these emotional outbursts in response to negative criticism of the writing is that the writers are equating that criticism to attacks upon themselves.  They claim, sometimes in explicit language, that their books are their babies and criticism of the book is therefore a personal affront. 

They claim that they don't mind low ratings (1- or 2-star ratings) or negative reviews, provided the review is constructive, is kind, is helpful.  Again, they want the review directed toward them, as the writers, not toward the readers for whom the review is intended.

Which all makes me wonder if in fact the writers were never writing for readers in the first place.  They were writing for themselves, with really no thought to the fact that other people would be reading, people who did not have the same passion for that particular book that the writer had.  Unable to separate themselves from their stories, the writers are unable to put themselves in the position of "mere" reader.

Very often there are other specific details about the writer's experience that raise some red caution flags. 

The writer who over-reacts to negative reviews often has a group of fellow writers for mutual support.  Most of them will have very little if any experience or knowledge of the writing/publishing business.  They are writing books based on personal experience or personal passion with the intent of sharing the writing as a direct extension of the self.  There is much less emphasis placed on how the resultant work will effect or impact or be received by the reader, and more emphasis placed on the personal expression of the experience or passion.  In other words, the writing is writer-centered rather than reader-centered.

The group is not, in fact, a critique group directing its attention to the writing, but a support group directing its effort toward the writer.  The writer is encouraged to write, but the writing itself is not critiqued.  Or if it is, the critique is more encouraging than critical.

Even after the writer has self-published the book, there is an entire community of writers who refuse to offer critical reviews because of their identification with the writer.  They admit they do not want to hurt the writer's feelings.  They refuse to leave a negative review or low rating because to do so would be to minimize the effort the writer put into the product.  They defend other writers, even when the writing is shown to be objectively sub-standard, and admit they fear retaliation if they even point out mistakes.  In some cases, these writers' works exhibit the same mistakes, suggesting they themselves are not qualified to provide the kind of writing-criticism the original writer needs if she wants to write for readers.

It's easy to make the leap from this to speculate that many of these hyper-sensitive writers have never been voracious readers.  They don't exhibit any kind of empathy with readers, but only with writers.  They seem unable to recognize the writing flaws that distinguish their writing from "good" writing, or at least writing that fits the standards generally accepted for successful popular fiction and non-fiction.  Even when they do admit, however reluctantly, that their writing mechanics may fall short, they offer a common set of excuses and/or justifications: They can't afford an editor, or the reader shouldn't complain about a free/inexpensive book, or the writer is a beginner and shouldn't be held to the same standard as professionals.  Again, the writer and her feelings always have priority over the quality of the product and the reader's expectations of it.

Anyone who disagrees with them is a bully, trying to kill their book and their writing career.  I'm not sure, at this point, that most of those writers ever really contemplated a writing career.  They have exhibited little to no professionalism in the production of their books that would indicate they've studied how to write and how to publish.  Instead, they have simply poured their "heart and soul" into words on electronic paper and uploaded them.  That's not a career any more than my buying a set of golf clubs would make me a professional golfer.

A common response to these meltdowns is that the writers need to develop thicker skins, and I've certainly expressed that feeling often enough myself.  After some of the most recent events, however, I'm beginning to think that's the wrong advice, simply because for these writers, growing a thicker skin is simply not possible.  Their books were really never intended to be shared with a wider audience than friends and family and supporters who would be encouraging and uncritical.  Their books really are their babies, part of themselves, created for themselves, even if the writers insist otherwise.  There's no indication that the writers did any kind of research to make sure they were producing a work that would be well-received by the reading public.  There are many more indications that they were simply writing for their own enjoyment.

And again, there's nothing wrong with this.  The problem arises when the writers forget -- and perhaps they never knew -- that when one writes for other people's enjoyment, one has to take their considerations and expectations first, not last.

Those of us who are avid readers long before we are compulsive writers know almost viscerally that books are not their writers.  Books are a creative product put into a public marketplace for consumption, discussion, comparison, and review, quite separate from their creators.  The conversations we readers have with each other about those books that fall short of our expectations as readers are not about the writers -- unless and until the writer inserts herself confrontationally into that conversation.

Sunday, May 11, 2014

I don't have to read a single word, and neither do you

You're probably thinking this post is going to be a defense of my oft-reviled tendency to rate or review books based on a reading of a single page or less.  Well, it's not.

Not exactly.

This is a simple challenge to all you self-publishing novelists whose digital sales are languishing and who have resorted to giving them away for free in attempt to boost sales without achieving the desired result.

Understand that I'm not addressing this to the writers whose books are selling to their satisfaction.  Nor am I addressing this to all writers who list their books for free.  No, I'm only addressing those who are dissatisfied with their sales and have chosen to give their books away as free samples but still haven't seen a significant rise in sales, whether of the same titles when not free, or other titles.  (Anyone else can try it, too, of course, but I'm specifically addressing that particular group.)

Part one of the challenge:  Take a look at any page of the digital text of your book.  First page, last page, third page of Chapter Twelve, it doesn't matter.  Bring it up on your Kindle or Kindle for PC or iPhone or any of the Kindle Direct Publishing emulators.  Not a PDF on your computer.  Not your original .doc file.  You need to be looking at the version that customers are going to be buying for their Kindles, iPads, smart phones, and so on.

Does your book have distinct paragraphs?  That means, is the beginning of each new paragraph clearly defined?  Yes, or no.  No other answer is possible.  Yes, the beginning is clearly defined, or no, it isn't.

Does it have block paragraphs?  That means, is the first line of each paragraph even with the left margin, and then has a blank line to separate it from the next paragraph?  Yes, or no.

Does it have indented block paragraphs?  That means, is the first line of each paragraph indented from the left margin and there is also a blank line to separate each paragraph from the next?  Yes, or no.

Does it have indented paragraphs?  That means, is the first line of each paragraph indented from the left margin and there is no extra line or space between one paragraph and the next?  Yes, or no.

You will have one Yes answer, and three No answers.  If you have four No answers, see me after class.  If you have more than one Yes answers, go back and review your answers.  If you can't figure out how to come up with one Yes and three No answers, see me after class.

Now, the second part of the challenge.  Look at random pages of several digital editions of books currently published by traditional print publishers.  If you can't afford to buy them, at least download some samples.  Go through the same four questions, and come up with the same single Yes answer.

Now, third part of the challenge.  Look at random pages of several digital editions of books currently published by successful self-publishing authors.  The easy way is to start with the front page of that listing on Amazon and just take the "Look Inside" preview.  By now you should be reasonably familiar with the four paragraphing style and be able to recognize very quickly which style is used in each book you examine.

If we number the four styles  -- none, block, block with indent, indent -- one through four, you should know what style yours is.  You should also have recognized that most, if not all, of the books you examined in parts two and three of the challenge use only the number four style: indented paragraphs without extra space between them.

Therefore, if you want to hope to compete with the established authors, with the authors who are selling their novels, you might to at least make your book look like theirs.  Nothing says, shouts, and screams SELF-PUBLISHING AUTHOR like no paragraphs, block paragraphs, and indented block paragraphs.  Figure out how to get your formatting to look professional.

(This challenge would also give you an opportunity to look at font styles and font sizes, if you're so inclined.)

Why is the type of paragraph such a big deal?  While it may not look to you like it should matter, it really does.

I'm going to assume you recognize the need for paragraphs on principle.  So that leaves out style number one.

While styles two and three clearly identify the separation of paragraphs, they also stop the reader's eyes from flowing to the next word/thought/action.  If you want your reader to keep reading, the very last thing you want her to do is . . . stop reading.  Not even for the tiny fraction of a second it takes her eyes to see that blank space, recognize it as just space, and then go on to the next line of text.  You want her to keep reading without a break, or at least until there's a break in the action, a change of scene, or whatever.  You'll indicate those with either a double break (the aforementioned blank line with or without a squiggly little design for emphasis) or a new chapter.

Block paragraphs work well for non-fiction if the author is presenting distinct information and wants the reader to take a tiny pause to think about what she's just read.  But fiction, when the author should want the reader to get into and stay in the story, any pause is just an opportunity for the reader to remember she has something else to do.  While you as the writer may allow her a convenient bathroom break between chapters, you don't want to be giving her those breaks every single paragraph.

More than one writer has excused the block paragraph format on the basis that it's easier on the reader's eyes.  While that's kind of the author to be so solicitous, it still means that the reader is given more and more and more chances to walk away, more and more chances not to be caught up in the story.  If you're so worried about the reader's eyes, make sure you don't use a tiny font, but don't make her blink and reread to maintain the flow of your narrative.

It's true, also, that in the old days of paper and ink books, extra lines meant extra paper, too, and we don't need to be that concerned about conserving paper when we're talking about digital books.  No, the only issue here is maintaining the reader's attention on the text.

Proper formatting of your paragraphs won't guarantee that you'll start selling 100 copies a week.  Proper formatting of paragraphs won't make up for poor grammar, ginormous plot holes, and TSTL characters.  But proper formatting of paragraphs may avoid some of the automatic turn-offs that come from readers who instantly recognize amateur presentation when they see it, before they've read a single word.

Wednesday, September 18, 2013

Almost perfect words

I got a very rude awakening the other day.  I learned that the Kindle Direct Publishing platform has instituted some changes.  More than likely, these changes were announced and explained in the e-newsletter Kindle distributes, but after finding too many errors in the first issue of that periodical, I confess I haven't been diligent in reading subsequent issues.  Not that I have a whole lot of time for that, but it is unprofessional of me, so I will try to do better.

Due to an issue that had arisen while I was formatting Legacy of Honor in preparation for Kindle publishing, I thought I would recheck the three books I had already published online. 

When I published those three, the Kindle program offered only limited emulation for the author/uploader to see how the document would appear on the Kindle.  Over time, that emulation has been expanded to include Kindle Fire, iPhone, iPad, and several other devices.   I strongly advise any author who has published via KDP to re-examine their documents -- and continue to do so on a routine basis -- to see if there are any formatting glitches that may come to light with this expanded preview capability and changes in device software.  For example, I noticed that the paragraph indents on one of my books should probably be adjusted to make for a better reading experience on all the various devices.  This adjustment is very easy to make, and of course can be checked before hitting the final "publish" button.

What I didn't know until a few days ago, however, was that KDP now has a spellcheck feature.  How long this has been there, I don't know, but I admit with some embarrassment that it was a surprise to me.  And it wasn't a pleasant surprise, because it brought up a list of misspelled words from one of my books.

I pride myself on my proofreading skills.  Do I claim to be perfect?  No, of course not, and especially not with my own work.  I know that it's far too easy to see what we expect to see when we're reading something we've written.  I still find errors in my stuff when I've gone back to reread weeks or months or even years later.  Not a lot of them and not all that often, but I do find them. 

Most often, however, those errors are misused/wrong words.  "That" for "than" or vice versa, or "from" for "form."  Or just a word left out.  But I'm a pretty good speller and a fair enough typist that I can rely on autocorrect and spellcheck to catch a lot of the basics and on my own good eye for the rest, even if it takes two or three or more passes.

Seeing that list of misspellings pop up from the Kindle spellcheck software rather alarmed me.  Then I read through the words that had been flagged.

An invented name.
A slang word.
An invented descriptive word.
A contraction.
A misspelled word.

In other words (pun intended), out of approximately 110,000 words, I had missed exactly one simple typographical error.  One. 

Needless to say, I immediately checked both of the other books.  Again there were invented names and slang and contractions, but this time not a single misspelling in either book.

Out of roughly 350,000 words, ONE was misspelled, according to Kindle's own spellcheck.

All three of these novels were uploaded from my original digital manuscripts, not from anything any publisher had edited or fixed or formatted or typeset.  These were not OCR scans of printed pages.  I will take the blame for any errors, but I will also take the credit for very, very clean writing.

The point of this?  Oh, partly it's just to brag and pat myself on the back.  But it's also to put the lie to those lazy and incompetent writers who defend their self-published pieces of crap with the old "It's impossible to catch all of one's own errors."

Kindle will do at least part of it for you, if you weren't diligent enough or competent enough on your own.  Can't you at least do that much?





Saturday, June 29, 2013

Words as therapy, words as dreams

One lovely Sunday morning in August of 1963, I hopped on my bicycle and pedaled to the little drug store near my home.  I purchased an ordinary spiral notebook there and pedaled home.  With pencil in hand, I sat down on the front porch of our house, opened the notebook, and began to write:

Sunday, August 11, 1963 (Morning entry)

I won't bore you with the teen-aged drivel-and-angst the followed.  After all, I was two months shy of fifteen so there was a lot of teen-aged drivel-and-angst to be written.

This was not, of course, my first foray into writing.  At a considerably younger age -- perhaps 9 or 10 -- I had started a number of the almost obligatory horse-and-girl fantasy stories, but by the time I reached junior high, my range of reading material had changed.  I was only in sixth grade, so not yet 12, when I began writing a pirate story in the style of Rafael Sabatini's Captain Blood, with a bit of treasure from The Count of Monte Cristo thrown in for good measure.  The summer before the diary was born, I had started what would today probably be called a dark ages historical romance, set during the barbarian invasions that collapsed the Roman Empire.  Though none of that manuscript remains in existence, I remember enough details of the story to know that my historical research for that period was pretty much non-existent!  Can you spell "anachronism"?

Sometime between the summer of 1962 and the summer of 1963, however, I began work on yet another novel, a contemporary mystery romance titled A Party of Ghosts.  The plot is kind of not really there and the main character is very Mary Sue-ish.  But there are themes of murder and sexual violence and non-marital sex and there may even be an illegal abortion.  This was pretty strong stuff for a 14 year old.  I'm not sure how far along I was on this novel by August of 1963, but I had definitely made a healthy start on it.  Writing the diary was not a new adventure for me.

Interestingly, though, I kept at it.  And I kept at the other writing, too.  Eventually, perhaps in the summer of 1964, I finished A Party of Ghosts.  The first draft -- chapterless and single-spaced on an ancient Remington manual typewriter -- is about 100,000 words, and I still have most of it.  There are a few pages missing, and I'm not sure why, but most of it resides in the file cabinet next to my desk as I write this.  Like the diary, it's filled with a lot of teen-aged drivel-and-angst.

I continued to write through high school, through my first stab at college at the University of Illinois, through my wanderings to New York and France and Spain and back again, but none of my fiction reached the completed manuscript stage.  And again, I still have a lot of it, tucked neatly in file folders or three-ring-binders.  Most of it is, um, not very good.

With my marriage in June of 1969, I vowed not to write fiction any more and instead to put my energy into being a wife and eventually a mother.  That vow lasted a few months.  But I had never promised to give up the diary, and it went on.  Yes, by that time, the diary was almost six years old.  It had gone beyond that spiral notebook and now filled several.

As the years went on and I continued to write fiction, I continued to keep the diary as well.  It now, almost 50 years later, comprises 23 spiral notebooks of various sizes and has recently entered the 24th.  I spent a great deal of spare time over a  period of about eight years actually transcribing it all, often horribly embarrassed in the process.  Was I really that angst-ridden at that age?  And "that age" wasn't necessarily as a teen-ager!

Would I ever want the diary published.  Good goddess, no!  I'd be mortified.  As Susan Douglas writes in the "Introduction" to Where the Girls Are: Growing up female with the mass media:  "Reading the diary I kept as a teenager is now excruciating, so mortifying that, if someone were to find it, I think I would blind myself with hot coals or simply commit hara-kiri.  I look back at my former self . . . the words she wrote in her spiral notebooks obsessed with two topics -- boys and sex -- and I wonder:  Who are you?  How could you have been so insipid?  Are you related to me?  How did you become me?"

When I read the first page of Douglas's marvelous, witty, and yet devastatingly honest book, I knew exactly what she was talking about.  But I also felt she had missed one point:  The importance of being able to look back at that former self.  Douglas's book, however, is not about the value of keeping a diary.  And keeping a diary is not a luxury everyone has or wants to have.

But as recent events have unfolded regarding the publication of unedited, authentic personal accounts, lost in the legal ramifications is, I believe, the true empowerment value of being able to express, without reservation and without qualification, one's feelings, all the drivel-and-angst that assails all of us at any age.

I cannot remember a time when I didn't want to  write.  It was never a matter of wanting to; I simply did it.  And I can understand that there are people for whom writing isn't the joy it is for me.  But as I've read some of the personal accounts of people who have endured traumatic personal events, more and more often I've read that they found some comfort, some relief, some healing in the venting of their feelings through writing. 

This kind of personal satisfaction doesn't rely on good grammar or perfect spelling.  The writer doesn't need to know or care about the difference between affect and effect, accept and except, writing and writting and written and wrote.  None of that matters, and it shouldn't.  That's the kind of writing that is for the writer.  She and only she is going to read it, and she knows what she means and what she wants to mean.  Eyes off and hands off her words.  They don't belong to anyone else.

That's how I feel about my diary.  When someone once read a part of it, I felt absolutely and totally violated, as though he had drilled a hole in my head and not only entered my thoughts and feelings but took them away from me, claimed them for himself, deprived me of my most personal possession.  For that reason, I never ever ever violated my children's privacy.  I never listened in on their phone calls.  I never looked through their dresser drawers.  When I found  a little "diary" that my daughter had written at the age of about 13 or 14, I returned it to her unopened and unread -- and it didn't matter that she was by then in her 30s!  The privacy of thoughts was sacrosanct.

When a writer decides to share her words, whether it's with one other person or with "the public," all those things that didn't matter before suddenly do matter.  Grammar and spelling and punctuation and using the right words.  All that stuff.  Why?  Because now she wants someone else to read her thoughts, and she has to use the tools of language to make those thoughts as clear as she can.  And the more people she wants to share it with, the more important her skill with those tools become.

As angst-ridden as my diaries from those teen-age years are, they are at least competently written.  As shallow and plotless and Mary Sue-ish as A Party of Ghosts is, at least a reader would understand what I was trying to say.  The verbs are right, the pronouns have proper antecedents, words are spelled correctly, commas are used where they're needed and not used where they aren't.

But that's because I always wrote.  I took the lessons learned in "language arts" class, as it was called at South Junior High in Arlington Heights, Illinois, and I used them to hone my storytelling skills.  These were the absolutely essential tools of the writing craft.  In all the years since then, I have often wondered if they might not also be the absolutely essential tools of living.

Maybe not.  Maybe now, in the days of Twitter and texting, when speed and brevity are more important, when feelings deeper than a :-) or a :grr: have no emoticons, when "IKR" is a whole sentence, what difference does writing make?

Writing makes a difference because we can't dream in emoticons and acronyms.  We still say "I know, right?!" in a way that means so much more than "IKR."  Maybe that will change with some future technology.  Maybe someday there will be tablets that you touch an icon and a whole emotional paragraph will appear on the screen or be broadcast through the speakers.  Who knows?  But for now, words are all we have to take what's in our hearts, our souls, our dreams, and make it real enough to share with someone else.

Sorrow shared is sorrow cut in half; joy shared is joy doubled. 

Sometimes it helps to share our sorrow, our grief, our fear, our anger, even if the only one you can share it with yourself.  Write it out, put it on paper or on the computer screen, and even if you don't share it with anyone else, even if you don't send that angry email or post that vicious comment or publish that scathing blog, just getting the words out can help.  Maybe it's just a vent for pressure and steam, or maybe it puts ideas into context, or maybe it helps understand.  If it's for yourself, that's enough.

But when the time comes to share the dreams and fears and joy and pain, then it matters how you write it.  It matters if you want someone else to be able to understand and feel what you felt. 

We do that, we who write, by following conventions so everyone is on the same page (pun intended).  Some of those conventions are so obvious they don't seem to need much explanation.  We all use the same alphabet, for example.  We all know what most of the common words mean: a, the, and, book, story, large, small, running, walking, eating.  We know, as both readers and writers, that something that doesn't follow those conventions won't make a whole lot of sense.

For example:

Deer Sirr:

I seed yoo wokkin outer the pos offiss yessaday an is hoppin yoo fown mi wollet gotz sum munny init.

Can you figure that one out?  Would it have been easier to read if I had written

Dear sir:

I seen you walkin outta the post office yestiday and I is hopin' you found the money what I lost.

In creating fiction, the writer has lots of options for re-creating the differences between what we consider standard English and non-standard.  Does the exact same feeling come across?  Maybe, maybe not.  But the compromise gives the same impression -- the person who wrote the note is not well educated and probably doesn't speak any more literate than he or she writes -- while still leaving the text intelligible for the reader without forcing her to back out of the reading experience to understand it.

This is part of the "invisible manuscript" technique that's so important for every writer.  You want the reader to forget she's just looking at letters and words on a page.   You want her to enter into the experience you're describing.

Some of us are lucky enough by fortune and experience to have acquired the language skills necessary to do that, and to have acquired them before we embarked on anything resembling a writing career.  For those who didn't, however, there are options.  Not everyone, of course, plans to become a writer.  Many who never wanted to write or who even actively disliked writing when they were in school find themselves years later wanting or needing those skills. Some never had the opportunity to learn.  But no matter what the reason, failure to write in a manner that allows the reader to enter the story rather than struggle to discern the meaning pretty much guarantees that the work will not find an audience.  If you want your story read, if you want people to get your message -- whatever that message may be -- you must make sure your writing conforms to the conventions established.

Does this mean you need an editor?  Yes, it does.

The necessity for a good, competent editor is never more apparent than when a good story that's been badly written is published, and all the world gets to see how terrible the writer is.  No matter how wonderful, how powerful, how emotional the story is, if the reader can't read it, all that wonder and power and emotion are lost.

Again:  If you are writing for yourself, if you are writing to get out the pain and fear and joy and frustration and excitement, none of it matters.  When you want to share that pain and fear and joy and excitement, it matters a lot.  And only a fool thinks it doesn't.



Friday, December 7, 2012

What have they done to my words? The Amazon formatting fraud continues

What follows is the text of my email to Amazon customer service regarding the Kindle content I downloaded last night.  I will post the relevant screen shots later today.


The Kindle content is "Stone of the Goddess" by Grizel Standilands.  I looked at the Look Inside sample, and it appeared fine.  The sample download, however, is formatted differently than the Look Inside feature.  It is in a different font and has no paragraph indents.  It is not easily readable.
I would like to buy this book, but I'm tired of getting Kindle content that looks good on the Look Inside feature and then turns out to be junk when I try to read it on my Kindle for PC.

I have deregistered, uninstalled, and reinstalled the Kindle for PC application literally dozens of times since these problems first appeared in July 2012.  Not a single one of the problems has been solved. 

Angels at Midnight by Norma Beishir
Danger at Mellin Cove by Rena George
Embrace the Wild Dawn by S.K. McClafferty
among others.

Amazon has taken hours and hours of my time in online chat and promise resolution, but nothing has been done.  I have been promised responses in three days, five days, a week, but I never get anything.  The people I chat with pay little attention to what I'm telling them.  For instance, the last time I got into an online chat, it lasted three hours, even though the question I asked at 20 minutes into the conversation could have been answered then, if the person had only been paying attention.

I have sent screen shots of sample pages showing what happens.  I have been told over and over and over that there is a team of specialists working on the problem and that it is an Amazon software problem.  I began reporting this in July 2012 and I have logs of all the chats to show that.
I know that it is perfectly possible for Kindle content to be formatted just fine to show correctly on the Kindle for PC app, because I read that content all the time.  If indeed the problem is in the software, as I have repeatedly been told by Amazon representatives that it is, then Amazon needs to fix it.  If, on the other hand, the problem is with the authors' formatting of the document that's uploaded to the Kindle platform, then that needs to be determined so the authors can fix their product.

I have the Kindle for PC app on two computers, an HP laptop operating Windows Vista and a Lenovo desktop using Windows 7.  I get exactly the same results on both of them when I look at the affected content.

The Amazon representatives have granted me some Kindle credit in compensation for my frustration and the time I've spent online with them.  I'm tired of giving up my time to this.  There is absolutely no reason why these books don't display properly on my devices.  And I am not going to go out and spend money for a Kindle device that I don't want and don't need and don't have the time to use, because I no longer have faith that these products would display correctly even on the Amazon hardware.

I am also a Kindle Direct Publishing author.  I have no way of knowing if Amazon has delivered my product in readable or unreadable condition to readers.  I have no way of knowing -- other than trusting the "preview" feature -- what my product looks like on any other device.  All I do know is that Amazon has been cheating authors out of sales by not addressing this issue for six months.

This email will be posted on my blog. 

Thursday, November 22, 2012

Words in response to the trolls and bullies

As difficult as it is to believe, I've been online almost 20 years.  Or maybe more than that.  I'm not sure when I got the first modem and the Prodigy software, but it had to be somewhere around 1992.

One of the first lessons I learned back in those old Prodigy days was "Don't Feed the Trolls!"  I remember a few of those first encounters.  Of course then as now I was mostly visiting threads and discussions about writing and reading, and we'd always get a few doofuses who wanted to make fun of women who read and wrote romance novels.  Then there was a guy who insisted no successful writer ever came out out of a critique group.  By the time I moved on to the GEnie network's Romance Exchange, or RomEx, and then to AOL, ignoring trolls was just another part of online life. 

However, I learned these lessons the hard way.  All too often I'd get suckered into one of those discussions, the kind that you can never win because they're designed that way.  Kind of like the old joke, "So, tell me, Bob, are you still beating your wife?"  There's no way to answer that and save face.

Yes, indeed, I often ended up in the role of the miserable, frustrated little soul, hunched over her keyboard into the wee hours, my brow furrowed in concentration, an enormous thought bubble hanging over my head with the words "Someone on the Internet is WRONG!" 

Most of the time, it wasn't worth the effort.  I changed very few opinions, if any, since all of us were safely ensconced behind our monitors and we didn't have to suffer much in the way of consequences.

The online world has changed a lot since then.  When I started with Prodigy and GEnie and AOL, DOS was still viable and there was no www, no Facebook and no eBay and no Amazon and no PayPal, no Twitter and no Pinterest and no YouTube.  Now we have all that, and more, and we still have the trolls.

As I've come back into my writing career (if you want to call it that) I've believed more than ever in the integrity of the words.  What we write has meaning and it has consequences.  If we are not prepared to accept the consequences, then we should not put our words out in public.  Once those words are out there, once we've hit the post or send or publish button, we've lost control of those words.  They are ours, but they are no longer ours alone. 

One area that has quite obviously attracted a lot of trolls is the whole issue of book reviews.  It's been a hot topic just on this little blog, even though I don't do any reviews here.  I do write about reviews here, however, and one of the issues I've addressed is the need for honest reviews, especially about bad books.

The sad truth is that there are a lot of badly written books out there.  The sadder truth is that a lot of those badly written books are published by their authors.  Amazon's Kindle Direct Publishing and Smashwords -- the two platforms I've used -- make digital publishing a snap, and far too many people have been seduced by that snap.  They've published too many books that weren't ready for publication, and worse than that is the fact the authors themselves weren't ready for the consequences.  They don't know why their books weren't ready nor do they know how to make them ready.  All they know how to do is lash out at the critics -- or anyone they perceive to be a critic.

I don't think I'd make a very good reviewer.  I say that even though I have been a reviewer in the past.  But the reviews I wrote for Rave Reviews and for the long-defunct online review site whose name I have completely forgotten were bland and formulaic and utterly commercial.  The opinions were mine and they were honest, but I felt as if they served little purpose other than to announce hey, random reader, here's another book you might want to take a look at.

As I've written elsewhere on this blog, the books I reviewed then were published by established print publishers who had a vested interest in making sure their product was literate.  That was one of the beauties of the old publishing machine.  You either wrote well enough to be published or you learned and practiced until you did.  When you wrote well enough to be published. . . .you were published, and it worked equally well in reverse:  If you were published, then obviously you wrote well enough to be published. 

Now there's no such validation, because anyone can be published.  There are no gatekeepers.

Books, however, involve a three-phase process -- writing, publishing, and reading.  Along with the traditional gatekeeping between writing and publishing, there was another between publishing and reading:  the book review.  Though less a true quality assurance function, reviews did serve to assist readers in making selections, especially in the romance fiction community.

But book reviews have proliferated just the way publishing has.  Where reviewers were few in number and were selected for publication in much the same manner as authors -- You had to have some credentials.  If your review was published in a reputable magazine, it was deemed to have some validity -- now anyone can be a reviewer, just as anyone can be an author.

So what the reader is faced with today is a double whammy:  A flood of self-published, unvetted reading material and a flood of untrustworthy reviews and recommendations.

Independent reviewers who try to wade through this tsunami are often attacked by self-publishing authors as well as their supporters.  This has been documented time and time and time again.  There are groups and individuals campaigning to force bookseller sites like Amazon and reader sites like GoodReads to limit reviews to only positive comments.  Reviewers are scolded if they aren't "nice" enough.  Reviewers who dare to express honest, personal opinions that happen to be negative have been the victims of cyber stalking, harassing phone calls, and publication of private, personal information -- all forms of extortion or blackmail to silence them. 

In other words, the authors whose books are receiving negative reviews have resorted to threats -- and in some cases carried out those threats -- rather than look to see if there is any validity in the criticisms.  And once the author has become angrily defensive about her work to the point of refusing to change one precious word of it, she's in denial and virtually incapable of seeing the errors that have to be corrected.

This is true even when the criticisms are leveled against elements of the book that are demonstrably and objectively inaccurate. 

For example, is the document properly formatted for digital publication?  Just about anyone can look at a Kindle device or the Kindle app for PC or Android or whatever and determine if a manuscript has been properly formatted.  Are there double- or triple-spaced breaks between paragraphs?  No paragraphs at all?  Are the margins reasonable, or too narrow or too wide?  These are the basic mechanical details of publishing the already-written book.  This is the process that makes the digital content look like a professionally prepared product.  This is what the "real" publishers do when they digitize a book.  The self-publishing author who doesn't care enough or know enough to format her product so that it looks professional probably doesn't care enough or know enough to write a good book.  Yet often when these formatting errors are pointed out in reviews, the authors or their supporters deny that the errors exist -or- they insist the formatting errors don't matter, that the reviewer is petty for pointing them out, or . . . whatever.

If there are spelling errors, punctuation errors, formatting errors, factual research errors and the author refuses to acknowledge them she is not going to be capable of handling the editing necessary to fix character motivation, plot continuity, and historical accuracy. 

Many of these problems used to be resolved in the critique group, contest, or "beta reader" process.  I don't know what happened to that.  I know that some of the free publishing sites such as www.booksie.com offer the writer the opportunity to receive feedback, but how much feedback is actually offered, what quality it is, and whether the authors take most of it is unknown to me, at least at this time.  Booksie, at least, allows the writer to delete negative comments.  Denial, denial, denial.

The ability of authors to deny or ignore criticism extends to more formal, commercial digital publication as well.  Ebooks aren't carved in stone.  When a book -- or its author -- receives too many negative reviews, the author can simply unpublish the book and then republish it, wiping the page clean of one-star reviews and negative comments.  Then all the fans and friends and family members and paid shills can repost the good reviews before the meanies get in there.

Reviewers have little recourse.  GoodReads, where I have actually begun writing reviews of some of the books I've read, defends readers more staunchly than writers and at least does not remove books solely because the authors have complained of too many negative reviews.  Once listed, the book remains along with all the reviews and comments.

I'm not afraid of the trolls and bullies.  I won't link to them or their websites, I won't name them, I won't out them from behind their screen names and avatars.  I don't care about them.  I write under my own name, and I will review under my own name.

As a self-publishing author, I care very much about the quality of the other books in the market place.  I'm not afraid to go up against the books published by the traditional publishers.  My work always has to stand on its own merits.   Nor do I fear competition from the hundreds, thousands of books offered at bargain prices by their self-publishing  authors, because I am confident my work is at least equal to if not superior to them.

If there is any threat at all, it comes from the poorly written, poorly presented books that make so many readers reluctant to even try the independent, small-publisher, and self-published fare.  There are no gatekeepers between the authors and publishing any more, and too few trustworthy gatekeepers between the publishing platforms and the readers, other than reliable reviewers.  Because some of the reviewers have either given up on "indie" books because of the actions of trolls and bullies, someone has to step into the breach.

I love writing and I love reading.  I love books.  Although my publishing portfolio isn't extensive, I think I have sufficient credibility to make not necessarily a good reviewer, but a good critiquer.  And the trolls and bullies be damned.



Saturday, October 27, 2012

"Perfect" is not a word I use very often

And with good reason.  Almost nothing is "perfect" anyway -- except some verb tenses.

That doesn't mean perfection isn't an acceptable goal.  The closer we approach it, the better we are at whatever it is we're doing.  Believing we've reached it, however, too often signifies we've lost sight of reality.  This is especially true of writing.

The other day, a reader pointed out to me that there were still some small errors in the Kindle version of Firefly.  As I explained to her, I knew about them but had left them because of my on-going battle with Amazon over the Kindle for PC application software.  These errors only appear on certain Kindle device displays, not on all.  And since the author has no way to know if a "fix" to an error will end up making it actually worse on other devices. . . . well, you see the dilemma.

At the time  Firefly was published on Amazon, the KDP preview only allowed the publisher (that's me) to preview how the document would appear on the basic Kindle device.  Amazon has now enhanced the KDP process so that the publisher has a variety of preview options and can now see how the document will look on the Kindle, Kindle Fire, iPhone, and others.  This is certainly an improvement.  So I was able to take the comments from this reader and check out what the errors looked like on the various platforms, something I had not been able to do before.

This allowed me to confirm that the formatting errors do appear on all the other devices -- but not, ironically, on the Kindle for PC!  So I've decided to proofread the text as it is previewed for the Kindle Fire and locate the errors.

Unfortunately, I found something else.  And this is why I cringe at the word perfect when applied to anyone's writing.

It's not a typo or a formatting glitch, nor is it a problem created by the conversion of the original 1987 Symphony documents into Word Perfect 4.0 for DOS and then through a succession of Word Perfect for Windows versions and finally into MS Word for the uploading to Kindle.  Yeah, there were a bunch of those, and they were a nightmare, and they provided the foundation for those lingering bugs in the Kindle version.  Nope, it's not anything like that.

It's a continuity error that's been in the book since that 1987 Symphony version.  I never caught it, and neither did my (cough, cough) editor at Pageant Books.  All the times I've read Firefly since, and especially all the times I've gone through it in preparing it for digital publication, I never caught this particular little mistake.

But there it is, so minor and insignificant that in all these years, all these readings, no one has mentioned it.  Does it affect the story?  No, not at all.  It can be corrected by deleting, or revising, a single sentence.  In fact, replacing one verb with another will do the trick, and that's probably what I'll do since I have to upload a revised version of the text anyway to fix the formatting errors.

The point is, even someone as nitpicky and perfectionist as I can make mistakes.  And having made them, I can miss them in proofreading and revising and editing and everything else.  Is it embarrassing?  Sure!  And do you think I'm going to tell anyone what it was?  Hell, no!  Neither am I going to make a big deal about the fact that the (cough, cough) editor missed it, too.

These things happen.  No one's perfect. 

But that doesn't mean we shouldn't try.  And it certainly doesn't mean we should excuse, dismiss, or -- goddess forbid -- defend our mistakes.  Admit it, fix it, and move on.





Sunday, July 15, 2012

And yet another update: Your words, my words, and Amazon

Okay, folks, this saga just goes on and on and on, with no resolution in sight.  And yes, this is in progress and will be updated as I get more information.

A second lengthy online chat with an Amazon service representative on Friday, 13 July 2012, yielded more misinformation, but it did not provide a workable solution to the problem.

Amazon is still saying that the problem with the formatting of Norma Beishir's Angels at Midnight as it appears on my Kindle for PC is caused by my Kindle for PC and that the only way to fix it is to de-register all the various Kindle for PC apps that have somehow appeared on my laptop computer, uninstall them, delete all of my Kindle content, and start from scratch.  This would involve redownloading 628 books.

When I tried actually installing the Kindle for PC app on my desktop computer, guess what happened?  ALL THE OTHER KINDLE FOR PC APPS also appeared.  Worse, however, was that some 54 of my downloaded books DISappeared.  Or so it seemed.  The suggestion I made to Amazon -- and documented in the chat log -- was that it looked like the 54 missing books could very well be free samples that I had downloaded, and some of them were for books that were no longer available on Amazon.  I had no desire to lose those free samples, at which point the Amazon rep told me there was nothing they could do about it.

In fact, she had no clue what she was talking about, because it turned out those missing books were NOT the free samples.  I still have no idea why there is a discrepancy of 54 books between my Kindle library as it shows for the Kindle for PC that I downloaded to my desktop computer and the Kindle for PC app on my laptop.

So I spent a good portion of yesterday -- Saturday, 14 July 2012 -- making sure I had back-ups of all my Kindle content.  Don't ask me how I did it.  You don't want to know.  At least not right now.  I finished that project this morning, which involved deleting and redownloading approximately 25 of the 627 books already on the device.

No one seems to know why that was necessary.

Sidebar update:  It appears, but it is not confirmed, that an update to the Kindle for PC app was made sometime in March 2012 and this may have caused all existing Kindle content to require the delete-and-redownload process.  Again, this is what appears to have happened, but I have no confirmation.  For some reason or other approximately 25 of my Kindle books had not been redownloaded at that time, and they required that process in order to facilitate the back-up process.  All of my Kindle content has now been backed up.


But with everything backed up as securely as I could make it, I decided to try downloading a new book.  On today's free list was Danger at Mellin Cove by Rena George.  I downloaded it and opened it in my Kindle for PC.  And the formatting was screwed up.



Although it's not easy to see on this screen shot, the problem is so bad that I cannot read the book:  At the beginning of each line of text on the left margin, about half of the first letter is missing.  The first letters of indented lines are fine; only the very left edge is affected.  And this goes through the entire book, making it unreadable.  One has to stop at the beginning of each line to figure out what the missing letter should be.

Here's the "Look Inside" version:




As you can see, this version has indented paragraphs, and all the letters are clearly visible.  Not at all like the version that showed up on my Kindle for PC with its indented block paragraphs and chopped off letters.

The  first thing I did was report this to Amazon via the book's page.  I explained what the problem was and that it was through the entire book.  About an hour later, I received a stock message from Amazon asking me where in the book the problem was and what the problem was.  As you can imagine, I was not particularly polite in my reply, since that is exactly what I had already told them.

About two hours later, I received another canned reply from Amazon informing me that due to the formatting error, Danger at Mellin Cove was being pulled until the problem could be fixed.  As far as I've been able to determine, the book has not been pulled and the problem has not been fixed.  Again, the problem doesn't show up on the "Look Inside" preview. 


Update:  16 July 2012:  Danger at Mellin Cove was briefly unavailable in the Kindle edition.  It is currently available for $1.54, which may be a conversion of the UK price.  I don't know. 

In the space of a week now, I've discovered two self-published books that are not showing up correctly on the Amazon Kindle for PC application.  I already know about the problems that cropped up with Firefly and which I now have no real way of verifying if all is well.  There was a huge and very nasty brouhaha in the Amazon "Badly Behaving Authors" thread a week or so ago because of another book that didn't show correctly on all devices; it was actually removed from circulation and some changes made, but that book, Wisteria Falls, remains not-quite-right on my Kindle for PC.

Self-published authors should not have to purchase every single variety of Kindle device in order to be sure their product is being published correctly.

Friday, July 13, 2012

Amazon formatting, part 2: Why the form of the words matters

For those who stumbled here without knowing what happened, here's the technical background on what Amazon's Kindle program appears to be doing to at least some of the books that are published via the KDP program.

Now, the next part of the discussion is, why does it matter?

Presentation of a digital book is important.  It's important for the reader, because the proper presentation makes the reading experience far more pleasant.  In fact, a poorly presented book can be virtually unreadable.  Readers notice.  Reviewers notice.

As I've already documented, I got negative reviews on Firefly for formatting errrors.  I learned subsequently that there may have been nothing I could have done.  Certainly I now know that neither the KDP preview nor the "Look Inside" may have provided an accurate picture of what the final product would look like.  And as I documented with the Smashwords edition, the various programs produce very different results from the same original document!

Many, many, many authors have received bad reviews because of the bad formatting of their products on Amazon.  How many of them, however, had no way of knowing what their product would look like?  How many of them were ultimately victims of an Amazon product that did not faithfully reproduce what the authors believed was a clean document?

Many readers have been turned off independent, small-press, and self-published authors because their products just don't look as good as a traditionally published book does when it is converted to digital.  And while the problems with competent writing and proofreading still have to be resolved by the authors, Amazon should not be contributing to a problem that may ultimately be costing them sales.

More later.  Yes, I'm publishing this blog serially, because I don't want to wait until I "get around to it."

Monday, July 9, 2012

Update: Those very expensive words

Well, well, well, well, well.  You learn something every day.

Or at least you ought to.

Over this past week-end, I began the process of publishing Firefly via Smashwords.  The exclusive listing for Amazon's Kindle expires on the 17th of this month, and I wanted to make sure I had sufficient time to check out the various formats offered by Smashwords.  After uploading what I believed was a "clean" copy of the file, I checked it using Smashwords' own applications.

This is a screen capture of a page from the Amazon Kindle version as it appeared via the Kindle for PC app, the copy that I downloaded when the book was offered free in April:


As I think you can see, the bottom line on this page reads: 
She was a good cook, she smiled proudly to
Now, here's the same passage as it reads in EPUB format via Smashwords' conversion:


Again, that line is down toward the bottom, and everything looks fine.

The third downloadable version I checked was the Smashwords Kindle/mobi version.



That stopped me cold.  Where did that screwed up font come from???

What I discovered on going through the entire file was that every time I used italics, the font changed from Times Roman to "ugly" courier for the entire paragraph, then switched back to Times Roman. 

I also discovered that the original Table of Contents I put into the Firefly file for Amazon, then revised for Smashwords but ultimately removed prior to uploading to Smashwords is still present.  This is, of course, a MicroSoft Word .doc file, which is what it has to be to upload to Smashwords.  And to Amazon's Kindle Direct Publishing platform.  I will have to go back through the file to find out where this TOC formatting hides and remove it.  Even though it actually functions as a TOC, I don't want it there.

The next thing I checked was the "preview" from the Kindle Direct Publishing platform.


Again, the single word is italicized, but nothing else.  This was exactly what the file looked like when I uploaded it originally.   There was nothing to indicate that the whole thing would appear on some customers' devices in "ugly courier."  The screenshot of the Amazon Kindle version above is, in fact, from this same original upload and not the later "corrected" one.  That's why I had no idea it would download in another format.

Here's yet another version, the "Look Inside" sample from the Amazon offering:




Once again, just the one word is italicized, the way it should be.  And this is from the current, updated, supposedly "clean" version, yet it now has lost its right justification, which shows on all the others!

This is how the various digital publishing software packages transform the author's file, and this is why it is so very very important that the author check each and every version.  Sometimes there may be absolutely nothing you can do.  But if you can do something and you don't do it, it's no one's fault but your own when a reader complains.

At this point, I'm not sure if the complaints about the "ugly courier" font on the reviews for Firefly on Amazon were because of something I did or something inherent in the Amazon software or something in the hardware devices the readers were using.  I do know that I've done whatever I can think of to make sure the version readers download is as close to what I want them to see as I can get it, but obviously it's not as perfect as it needs to be.  So I'm going to keep working on it.