RLLauthor@outlook.com and @RLL_author GO TO AMAZON KINDLE STORE AND TYPE RLL. YOU WILL FIND MY BOOKS.

Showing posts with label KINDLE FORMATTING. Show all posts
Showing posts with label KINDLE FORMATTING. Show all posts

Friday, 7 June 2019

QUALITY CONTROL IN AMAZON KINDLE BOOKS: A REPORT FROM A FUGITIVE.


Amazon warned me it had updated the e-book process behind the curtain. Updates are constant. This update, though, is worth a mention. It’s far easier for Amazon to point out quality issues concerning my e-books. I thought over all the gruesome alerts I’ve been sent since the update kicked in…oh, no, there aren’t any on file. Why not? Just lucky, I guess. That must be it. Just lucky.
   I recall the searing memories of THAT TIME.
   THAT TIME was the time I spent eight ultra-long weeks formatting my first e-book. And formatting. Then formatting. Formatting some more. With a bit of formatting thrown in. Followed by a hint of formatting. With a smidgeon of formatting after that. On the menu tonight and every night: vindaloo and…no, of course not. Formatting. With a hint of lemon.
   No, I didn’t learn the hard way.
   (A lie was told there, surely.)
   I learned the very hard way.
   (True.)

*

I stared at those files from front through to back and back again. That was the only way to fly. I told myself this. No matter how drudged-up the drudgery was, I had to check every effing page from front to back and all the way back to the front again.
   Good job I did. That way, I discovered formatting glitches that only showed up when you flipped back for more than four pages at a time. There’s page 77. Let us take a dainty trip back in time to page 76. No problem. Now let us traipse to the very end of the book, and walk all the way to the start, page by bloody page.
   From page 82 we run to 81, 80, 79, 78, there’s page 77, and now page 76 with no prob…what the blue veiny cheese is going on?! Half the page is in print twice the size. How? Why? And what’s this glitch that doesn’t show on the page unless I am digitally thumbing back for more than a few pages?
   Invisible gremlin is invisible. (Shakes fist at invisible gremlin. Spins slowly in circle, hoping to shake fist in general direction of invisible gremlin.)
   I’d uncover the formatting problem in the original file and erase it. Occasionally, I’d accidentally import a gremlin from a wildly different file. Or I’d find myself using an older file that had ancient formatting built into it where you couldn’t see anything. There’s a space in the file, and, though there’s no text at that space, the text that could go there would definitely be in a green font. (For reasons beyond me.)
   And I’d change the green font to black. The invisible formatting problem went away.

*

When I downloaded free samples of books, I checked formatting in those and discovered that paging back through someone’s story spewed up all sorts of nonsense you didn’t normally see if you were just going forward. What if you were interrupted turning a digital page and you moved back to read the last paragraph again? All these spanners falling out of the machine, why, they must come from somewhere.
   Belgium.
   They came from Belgium.
   (Unable to verify this at the time of writing. But definitely Belgium, though. Known for its spanner manufacture. I almost typed spaniel there. Searches internet for Belgian spaniels. Discovers trade in spanners offloaded from Mozambique to Belgium. Nothing much on the Belgian spaniels, though.)

*

Old news. I thought I’d revisit that old news on seeing the new news that I’ll receive direct updates on the Amazon bookshelf, warning of quality issues. Quality? That means formatting issues, and I buried most of those in a deep grave during eight weeks of teaspoon-based digging.
   Except…I remember one persistent glitch I couldn’t shake for a year, after publication. One night, I resolved to bury that gremlin. I tried everything. Except one basic thing. That was all I had left. The last item on my list. Yes, I should’ve gone straight to the last item on my list.
   Life never works out that way. If I’d skipped the first thing to go and check the last thing, the last thing wouldn’t have been the very thing – just one more thing. It’s always the last thing, no matter where it is on your list. If it is on your list at all.
   Well, I had a list and I exhausted it. This is a detour down memory lane, into levels of formatting that still apply, even if the file processing procedures rolled over and died in the name of simplicity. Of course, I welcomed the simplicity. Shame it didn’t rear its head earlier.
   But nay, I must not speak of the dreaded Table of Contents and its associated file madness that almost worked for me. Damn that five-minute window of opporchancity in which it all looked golden. As golden as a desert mirage. And as useful. I found my own simple solution for dealing with that nest of vipers. Confront complexity. Kill it with fire. Eat a hearty meal. Think no more of that nonsense.
   So what are quality issues? The things I’ve already described. Imported fragments of troublesome text that mess with the flow of the book when clicking on a chapter link or running back and forth across text. I nailed all the obvious problems in eight weeks of dealing with a single file, and never had a major beef with Amazon over quality warnings. Never had a minor beef, either.
   I went from formatting a book in eight weeks to formatting a book inside a day. After that, I had my story templates set up so that I’d adjust formatting on the go. The learning of it was tedious, performed with intermittent internet access. But once done, I was set. I threw myself at the task with relentless amounts of coffee powering my endeavours. And I was all the better for that caffeinated preparation.

*

Yes, I’ve written about all this nonsense before. I never expected to write of it again. Yet here we are, with the news down from Amazon’s mountain. I’ll be more connected, more involved, with receiving quality warnings over the formatting of my books. Technically, not receiving quality warnings.
   In talking about writing, you talk the talk no one wants to hear about. There is drudgery. It can be tax drudgery, official form footeriness, or the emptiness of the coffee receptacle calling to be refilled. Technical crap clogs your day. On some of those days, back when I toiled in the wilderness for eight weeks, I’d encounter a glitch that occupied me all day long, and I’d have nothing to show for my toil as the sun crashed over the horizon.
   I’d have to wait for a new dawn, and the opporchancity to gain a slice of that limited internet access, before I’d see the mouldy fruits of my efforts crawl into the shadows to die their lingering deaths.
   Scribble note on piece of paper.
   Attempt to fix the problem right there.
   Fail.
   Think of another solution.
   Fail.
   Leave the library and head home to the office. Thrash out the problem on a bloodstained floor. Imagine that I’d fixed the grief. Believe that. Start again the next day, and the next. I don’t know how I managed. With a faraway look, a steady supply of triple-choc muffins, and the patience of two saints – borrowed for the duration.
   Flashback. I blasted off from the library’s internet access and installed my own. Today, I could devote an entire day and night to online research into a formatting problem. No need to go through driving rain to head back and forth, when back and forth is done at the click of a mouse.
   Did much else change? File processing grew far easier. There were changes that never affected the type of books I put together. For example, if you constructed a book with a load of charts and mathematical tables, I’d imagine you saw your share of battle in the formatting wars.

*

Once I found my way onto the formatting path, out of the deep thickets, I was fine. I could’ve paid for the formatting. But what would I have learned from slapping the cash down? How to do things the easy way, without picking up a good working knowledge of the clockwork mechanisms holding my books together?
   I’m not knocking paying for formatting if you can’t stand the drudgery. Though this is writing under discussion. In talking at any length about writing, you talk the talk no one ever wants to hear about. There is drudgery. Word on word, paragraph by paragraph. Rewarding drudgery, to be sure.
   Ah, the glamorous world of typing for hours on end with no end in sight. I long-ago rejected the notion of voice recognition software when the voice recognition software rejected my Scottish tones. So typing it must be. In my alternative history of the world, Scotland had a stranglehold on computers…and the voice recognition software in that world…is pure gallus, byrahwey. Stoatin’.

Saturday, 14 February 2015

AMAZON AND KINDLE PUBLISHING FILES: A REPORT FROM A FUGITIVE.

Farewell, People's Republic of China. We hardly knew ye.


*

I'm not talking about the People's Republic of China. But I often thought of China when I created PRC files for Kindle books.


*

Amazon no longer supports the PRC file it pimped out to me at every fucking opporchancity. Write your story. Edit your story. Publish your story - by converting it to PRC.
   And don't forget to drop two important pieces of metadata in there before hitting the BUILD button. Fare thee well, BUILD button. Your like, we shall not press again.
   I won't speak of the arcane process involving the Table of Contents and its Frankensteinian creation. There was a ceremony for this, and...


*

My legs! Argh!
   Don't think that knee will ever be the same. It hurts on rainy days.
   Anyway, I didn't use the arcane ceremony - for the simple reason that I couldn't get the fucker to work at the last gasp.
   Instead, I used the outré method of dropping two lines of code into the PRC file's metadata - forcing Amazon's Kindle system to see my Table of Contents and, good gravy, nod in the general direction of the start of each book.
   What fresh hell is this?
   I believe a lot of writers uttered that phrase to themselves as they went through this non-process.


*

And it's all gone. Amazon shifted over to MOBI files. I didn't shift over with them. Instead, I opted to test the basic Microsoft Word file.
   No fucking around with software, metadata, no remembering codes, no fucking nothing. Write your story. Edit your story. Publish your story.
   Done. Melissa C. Water, mentioned elsewhere on the blog, wanted to put out some of her stories. I offered to format the books, using basic Word files, to see how things looked.
   After uncovering one invisible glitch, I saw that the system took the strain. Farewell, PRC. I'll miss you like rabies. Well. Damn.


*

I don't deny, I learned a lot when I put those files together. They were great for testing. But Amazon keeps advancing its Kindle products, and who am I to stand in the way of Darth Bezos?
   Besides, provided my book is formatted to within an inch of its life, just using the Word file takes away an awkward moment or two of coding shit that I need never remember again.
   And the world is a better place for that.

Tuesday, 8 October 2013

KINDLE FORMATTING. SIZE-CHANGE GLITCH.

This glitch took a little while to spot. I believe authors should know their work front to back and back again. Because I checked my books that way, I found this quirk on Amazon's Kindle platform...
   Sometimes, seemingly for no reason, when going back through a book, the size of text would balloon all by itself.
   Reading a page in a small font...
   I'd find myself staring at a piece of text that was filling the page.
   Then I'd find myself back on the much smaller size I'd originally selected.
   So I adjusted the text itself to see what difference that made. Advice? None. Unless you count...
   Ask Alice.
   The problem is thrown at you when reading text that's broken into blocks. And only then, when reversing through the book by more than four pages.
   THAT is why it took me a little while to fathom. You could track back through three pages. Nothing.
   The problem appears more frequently if adding scripts to a work. Writing some form of movie script or running a section of a play.
   Here's the grief. Regular paragraph returns, employed to show space, don't work one after the other. They only show up on the Word file, and not on the converted file built for the Kindle.
   Multiple manual line breaks do show up, but you don't want to use too many of those. Especially if you are compiling one-line lists of things - in a table of contents, for example.
   A single regular paragraph marker will show up as a space if it is preceded by a manual line break. That can cause complications. Fortunately, the reverse arrangement works. Paragraph marker followed by manual line break.
   Somewhere in all these combinations, you'll uncover awkward quirks. To avoid awkwardness when compiling blocks of text, use manual line breaks for all but the last line of text. As shown here...


   In the block running from VAMPIRES through to chapter THREE, each line ends with a manual line break. (Press shift and return together for that effect.) However, the last line must end with a paragraph marker. (The return key, alone, for the end of the chapter THREE line.)
   My entries for blogs are single sections, and are treated as last lines for purposes of choosing the finishing symbol - a paragraph marker in each case.
   Sticking to that pattern avoids all sorts of quirks and gremlins. With the notion of providing a script caught between sections of text...


   ...the line of dialogue ends with a paragraph marker. And the space between lines is registered using a manual line break. UNTIL the last line of dialogue before the next block of regular text.
   Then the position reverses. The line ends with a manual line break and the space is registered by a paragraph marker. See Moff Larkin's line about integrity in Hull for the shift.
   That change removed a lot of gremlin-based activity from my work. It'll only apply to your work if you provide one-line lists, or slices of text resembling a play.
   Look out for spaces in Kindle formatting. How to apply those spaces between blocks of text. And run through your work, page by page, once you've slapped a prototype copy on the Kindle.
   Back the way, as well as forward.
   Keep experimenting with formatting. Find what works for you, based on the tools you use and misuse.

KINDLE FORMATTING. CENTRED CHAPTER TITLE GLITCH.

In the last post I mentioned placing a paragraph mark at the start of a chapter, to negate an awkward formatting glitch. That glitch applies to centred chapter headings. Here's the tale...
   Does this happen in your Kindle books?
   When using Kindle to jump from the table of contents to any chapter, the centred chapter heading flicks to the left of the page. Go back or forward one page and return to the chapter start and the heading changes size slightly as it reverts to the centre.
   Adding an extra paragraph mark to the Word file at the top of the page kills this glitch off. Here's how...
   My stories use manual chapter links. (As opposed to the automated feature provided by Microsoft.) For ease of navigation, I set up my own table of contents and list chapters and special features there.
   Each heading has a hyperlink leading to a bookmark attached to the actual chapter title further in. To save bother, I set that stuff up in template form.
   For example, my FICTION FACTORY stories are in seven sections. VAMPIRES, shown below, started in the template as...

TITLE.
ONE.
TWO.
THREE.


BEHIND THE SCENES – CONSTRUCTING THE STORY.
ALSO AVAILABLE.
ABOUT ME/CONTACT ME.


   I just fill in the blanks by writing the story. Using Microsoft Word, you must go through the menus Tools, Options, View, Show. Tick the box for Bookmarks.
   Then you'll see bookmarks you've added. They show up as grey square brackets.

[CHAPTER TITLE.]

   Each chapter title is hyperlinked back to the table of contents. Hence all the underlined blue text in the Word file. So what's the problem?


   You can see by the purple text that I accessed the first chapter in that shot of the manuscript for VAMPIRES. I was double-checking the glitch was gone.
   If you generate a chapter with a centred title on one line...


[CHAPTER TITLE.]
   ...then you create a curious glitch when using the table of contents to reach that chapter. Clicking on ONE. NO STRINGS SOME RULES. leads to...


    In the Word file, you'll see that the chapter title is on one line, and that's true of the hyperlink too, but the grey bracketed bookmark is spread over two lines thanks to that extra paragraph mark inserted at the start of the page.
   If that bookmark isn't split, there's a glitch. You get that annoying unannounced alteration in size of text and a shunt to the left.
   So. Keep your title in one piece. And keep your hyperlink in one piece. But add an extra paragraph marker at the start. Highlight that AND the title line for inclusion in the bookmark when you go to add the bookmark.
   No more glitch page problems.

*

Note...



   There are spaces between blocks of text on this page. Normally when going from paragraph to paragraph, I use paragraph markers by hitting enter. Return. Carriage return.
   However, when creating one-line lists, I press shift and return together to generate a manual line break. That works until the last line in the block, which must be a paragraph marker. The space between blocks is then activated by another manual line break.
   Doing that avoids a devious glitch, which I'll cover in the next blog post. It's only really of concern when creating lists, or scripts for plays and movies.


Monday, 7 October 2013

KINDLE FORMATTING. PARAGRAPH INDENTATION.

This next piece proved useful to people, so I’ll repeat it here with a few visuals thrown in.

To turn my story into a Kindle product, I use MS Word and convert the file to PRC using Mobipocket Creator. (PRC is nothing to do with China, as far as I know.) Go to the Kindle section of Amazon. Find a book, any book, inviting you to LOOK INSIDE!
   Do just that.
   What are you looking for? The first line of the story. Chances are, that line is indented. Amazon has a default setting within its publishing factory, which has given rise to this decidedly non-paperback phenomenon.
   When I was struggling to deal with the format of my first self-published manuscript, I soon discovered this joyful stumbling-block. That’s what the Previewer is for. Well, how do I get my book to look like a book? With the first paragraph free of indentation…
   Solution?
   I couldn’t find one. Answer – chip away at all possible permutations until I found one that worked. This solution relates to using Microsoft Word for the original text, before it goes through the caterpillar-butterfly transformation.
   Start with the chapter title. Type carefully. The chapter title ends with a tap of the return key. MS Word recognises this symbol as a paragraph mark.
   On-screen, the symbol resembles a capital P flipped to face the other way, with the hollow section filled in, and two legs to stand on instead of the usual one leg.

 
   Some of you may think of the return key as the enter key. Others might still call it the carriage return key. I feel I must refrain from making comments about age.
   Follow that single tap of the return key with manual line breaks. Hit the return key and the shift key simultaneously. That generates a manual line break. On-screen, the symbol looks like an arrow coming down and veering left.


   I use three manual line breaks like that before I start writing the first paragraph. The general recommendation is that you never use four or more.



   That should do the trick. Chapter title. Paragraph mark. A number of manual line breaks to suit your own taste – no more than three. (People like to read books on their phones, and more than three breaks will cause trouble for those readers.)
   With the title/paragraph mark/manual line break sequence in place, the first paragraph of a chapter then loses the annoying (unseen) default indent.
   You can’t just use paragraph marks one after the other, as they don’t show up when used in a straight sequence. Once converted to Kindle, they might as well not be there – leading to no space between chapter title and first line. Awkward, unless you are aiming for that style.
   (However, note that, in the above screenshot on chapter links, I place a paragraph mark at the top of the page before the title. This removes a formatting glitch from the book in relation to hyperlinked chapter titles. The title shown isn’t hyperlinked, but I use the extra paragraph mark as a matter of routine. This extra paragraph mark doesn’t show up in the finished product.)

*

For breaks within chapters, I separate the sections by means of an asterisk.
   End the section of text with a paragraph mark. (The return key again.) Next, add a manual line break. (Shift and return. Not one after the other. Together or not at all.) Then type the asterisk, followed by the return key.
   To end the sequence, hit shift and return together. After that, type your new paragraph. Go back and centre the asterisk. The line break above the asterisk should also centre, though the one below should not.

 
 
   Beware. If the next section opens with direct speech, you may find inverted commas starting with closing quotes instead of opening ones. Some fine-tuning is required.

*

Why place an asterisk between chapter sections? The reader will always see the asterisk. If you leave a blank space between sections, that space can be lost in the Kindle shuffle, depending on font-size. A new section, without indent, should indicate where the next scene kicks off. The best solution is to have some form of character, preferably an asterisk, right there as an obvious visual cue.

*

For authors who wish to follow the advice, remember – this arrangement worked for me. You may be doing other things in the background, or foreground, bringing my advice into conflict with how you run your office. Solution. Keep trying.
   All of my books get around the Amazon default setting of the first line paragraph indent. Is this something readers are bothered by? We’re in the Twilight Zone on that one...
   How far does an e-reading experience stray from the paper one? An army of readers, used to paper publishing conventions, will want something that resembles what went before. With all the advantages e-reading brings, into the bargain. (Instant dictionary, etc.) In another generation, who knows...
   Some readers will convert completely. Others will mix and match between paper and e-reading. A few will sample then reject outright, clinging to the familiarity of the past. There is a cry for “proper” books, whatever those are.
   If you feel that you are going to alienate many of your readers by dropping traditional publishing conventions, do your best to take account of this. Though remember – there was resistance to the end of the one-page paragraph. Robinson Crusoe would be a touch easier to read if rendered in smaller chunks on the page...
   For my part, I couldn’t cut loose of an established publishing convention even though I embraced digital publishing. I wrote my fiction that way anyhow, and stuck to that format. To first para indent or not is your choice.
   If it makes production of your book easier and you don’t receive thousands of complaints, ye are harming none and saving yourself some bother if you decide to stick with the Amazon default.
   We’d all like to think it’s what we write the readers are interested in, and not how we encode our scribble...

*

Paragraph indentation itself is handled in the Format box. Highlight the text you want to indent. Inside the tab marked Indents and Spacing, there’s an option for Special settings. To generate paragraph indents, set the feature to First line and select a measurement. I use 0.5 cm, as shown in the screenshot.



   Once you’ve set up the indentation, that’s it for the rest of the text unless you put in obvious breaks. Then you’ll have to highlight again.
   I can’t cover all the quirks here, as I don’t know how you write your stories. But you’ll see how things pan out as you go.
   While your attention lingers on that screenshot…
   Line spacing should be set to 1.5 for the eventual conversion to Kindle.

Friday, 23 August 2013

USING HTML CODE ON YOUR AMAZON PRODUCT DESCRIPTION.

The thing I hated about creating book blurb for Amazon? I'd use a combination of an excerpt from the book and a commentary about the story. Fine. Except that the slice of fiction lost italics.
   How to fix that problem?
   Encode the book description with HTML.
   Hugely Tiresome Muddling Laborious code.
   I've just been experimenting with the code, altering my Amazon Kindle blurb.
   Here's a link to the official Amazon page. OFFICIAL. That page shows the HTML code acceptable in a book's content, but there's a sub-heading for code you can use in the blurb. BLURB.
   There's not a lot of code available. When I say that, I'm talking about official code. Supported code. Code the Amazon publishing factory will permit you to use.
   Even the Amazon publishing factory doesn't like the code that is supported. I'll return to that.
   So how do I use the HTML code to change the look of my Amazon blurb?
   I want to make the title VAMPIRES. appear in bold italic type. And it looks that way in the Word document. Cut and paste that text into Amazon's publishing factory, and the effects are stripped away.
   Those effects must be reintroduced using HTML code. Find the code for the effect you wish to use. Type it where you want that effect to start.
   There is an off-switch for that code - add a slash to the code when you are finished. Example...
   VAMPIRES.
   The code for bold text is <b> and the off-switch is </b>, so I'd set this up...
   <b>VAMPIRES.</b>
   That's it. Once you've arranged this fiddly piece of work, Amazon will raise an objection. Here's an example...


   You'll see I've used codes for bold, italic, and a line separating sections of text. I don't recall adding a slash inside the <hr> code for a line. But there it is.
   The red text is a warning you can ignore, provided you are using basic things like commands for bold.
   Note the number of characters left. Usually, I'd write a short blurb for Amazon products. Occasionally, I'd go into more detail.  HTML coding counts against the number of characters.
   Remedy? Make it fit. Edit the text. You are in the writing game, after all.
   If you go surfing the web on a spider's surfboard, and pick up other HTML coding that's not supported by Amazon, you'll risk receiving the second red warning.
   The first one is okay. Ignore it. Save your publication page. The second warning kills your work off - and Amazon refuses to save changes made.
   If that happens, resort to trial and error message. Keep chipping away at the nasty code until Amazon accepts the saved changes.
   Then publish. Wait for the product to cycle through Amazon's system. The updated blurb will appear long before Amazon e-mails you to say the book is ready.
   Get it wrong? Wait for the book to become available on your publishing bookshelf, and make changes. That's the most annoying thing - the cycle-time if you have to fix errors.
   I had nine products available on Amazon when I decided to upgrade my book descriptions. The first one was HTML-encoded the night before, so I could sleep on it and see the effects come morning. Then I switched to production.
   Here's the before/after look to the blurb for WEREWOLVES. I didn't go over the top with dancing figures and spotlights. At that reduced size, you can still see the differences. Which is my point...

 

    In publishing for Amazon, we often live in a thumbnail world. View everything at reduced size, to see if you can see differences.
   Click on the cover below to see the updated blurb for WEREWOLVES.