Saturday, May 4, 2013

"Kindle Publishing Guidelines" Updated Again (2013.3)

Having released version 2013.2 of the Kindle Publishing Guidelines just a week ago - on April 27th - to incorporate support for audio/video content in reflowable ebooks (Section 6), Amazon today released another update with considerably more changes. Many of these are editorial in nature, showing that they are at least attempting to address the poor writing quality and general lack of clarity that has plagued the Guidelines since its inception.

As with version 2013.1 released back in February, I have highlighted and annotated all the changes made in this edition since the last one, and you can upload my version from the link above, since Amazon themselves provide no change log, or even a notice when a new version is released. I've just learned to check it regularly, and did so today quite by chance. I just happened to be going through copy-editing revisions for the new book, and while doing so for the section that covers documentation I thought I'd have one last look before the final draft is locked.

As far as functionality and content changes to the Guidelines, the most significant among these are:

  • A new section (3.1.9) added to the General Formatting Guidelines for "Customizing Font Selection" which seems to address an apparent problem with improper styling of primary embedded fonts (p.14).
  • Brazilian Portuguese (bp) added to the -locale language option for Kindlegen's readout (p.8).
  • Support for right-to-left vertical scripts and Japanese Ruby script added for the Paperwhite and newer Fire devices (p.11).
  • A large number of clarifications and additions for basic text formatting, which apparently address the improper use of imposed font styles and colors in reflowable ebooks (p.11).
  • Important clarification regarding the HTML cover page exception in Section 3.2.3 (p.16), which now specifies that this applies only to reflowable ebooks (although the conflicting and inaccurate statements in Section 4.3.7 still stand).
  • Some additional emphasis added for preferring tabular data over images (p.25).
  • Guide items are now "highly recommended," although they still remain optional (p.28).
  • Region Magnification pop-ups should not be positioned "too close" to the edge, in order to prevent content overflow on different devices (p.32). This is appended with one of several new notes advising content creators to test their files on as many different devices as possible. The unwritten implication is that Previewer is not accurate enough to rely on for final testing.
  • An additional line added in Section 4.2.3 to emphasize the recommended use of CSS background image embedding over HTML <img> tags, even though nearly all of Amazon's own sample files use the <img> method, as does Kindle Comic Creator (p.33).
  • Reiteration that there should be one CSS file per HTML page, and that its content should be relevant to just that page (p.33).
  • If back cover images are added, barcodes, etc., must be removed, and there should be no text popups included (p.34).
  • The use of non-breaking spaces for text alignment is now forbidden, rather than "limited" (p.36).
  • Two new points have been added to the "Best Practices" section for testing Kindle books (Section 9.1), one for checking text/background settings in reflowable ebooks, and the other to assure that all region magnification panels function correctly in fixed layouts. Similarly, some clarification and expansion has been added to Section 10 on Kindle Quality Guidelines (p.65).
  • A few of the supported HTML tags are now deprecated, including <big> (but, ironically, not <small>), <center>, and <font> (Section 11, p.66-7).
I have not highlighted the additions for audio/video support that were added in version 2013.2 released last week, but they are there in the first two paragraphs of Section 6, for those who are interested. See my comment on this issue in last week's post on the topic.

All in all, no major changes in this edition, but some welcome editorial revisions nonetheless. Changes that have not been made that I am waiting for include:
  • Increased file size limits for images to allow the recommended 2x resolution for image zoom (which would require a file 2400x3840 for the HD8.9" Kindle), or the removal of that recommendation
  • A clarification that the RegionMagnification metadata value is no longer valid (or at least the removal of it from the metadata table)
  • Statement of recommended aspect ratios / image dimensions for page sizes, so that they display correctly in two-page spreads (currently odd numbered resolutions result in gaps between the pages, even when "page-spread" is chosen as the Spine property rather than "facing-page")
Still needing fixed in the device software itself are these major issues:
  • Page-spread support on all devices for all book-types
  • Live text functionality and bookmarks for all fixed layout ebooks, which should never have been disabled in the first place
  • Layout-blank, which does not work correctly in almost any case
  • Missing menu links on the newer Fire devices when the "children" book-type is chosen
I mention these only in the off chance that someone from Amazon is actually paying attention.

Sunday, April 28, 2013

How to Make Kindle Comics - Final Draft Complete

After numerous additions, several revisions, and half a dozen lengthy delays, the final draft of How to Make Kindle Comics & Graphic Novels is finally complete. 

Since I began this project back in December, Amazon has made major updates to the entire Kindle Fire line, upgraded Kindlegen, and released Kindle Comic Creator, all of which threw my efforts into sudden turmoil. My only hope now is to get through one last copy-edit pass and convert the thing to ebook format before a new line of Kindles is released!

The final manuscript comes in just shy of 70,000 words, with around 160 images. Additionally, I have added a number of new features to the Advanced Template (Version 3.0) to provide further examples of concepts covered in the guide, and this will be uploaded when the ebook is released.

My current plan is to upload the file to NetGalley and let it run its course for two or three weeks before the official launch, putting it somewhere around Memorial Day. This is what is called a "soft launch" in publishing circles. Some would call it sloppy. I call it necessity. Since I do all the work myself from start to finish - research, writing, testing, art, layout, and editing, not to mention marketing - and do it all on nights and weekends in between my real life as a bookseller, it's difficult to say when any given task will be checked off the never-ending list.

But this was the big one. From here it's all downhill.

I want to thank all of you who have waited patiently, and promise that I'll get the ebook posted up as soon as possible.

Saturday, April 27, 2013

Audio/Video in Kindle eBooks

I mentioned in a post last month, Amazon's recent updates to the Kindle Fire software added audio/video support for the first time to the Kindle devices. Previously, multimedia support was only available in the Kindle for iOS app, which made it more or less irrelevant to invest the time and effort necessary to produce ebooks with these added features.

Now, however, all of the latest generation color Kindles have been given support for audio and video content. To that end, Amazon last week released an updated version of the Kindle Publishing Guidelines to incorporate this change. This is, in fact, the only change that has been made to the Guidelines, and consists of just a single change found on page 47 at the top of Section 6 Audio and Video Guidelines, where two lines have been altered to read:
Kindle Edition (sic) with Audio/Video content is available on Kindle Fire (2nd generation), Kindle Fire HD, iPad, iPhone, and iPod Touch.
Previously it simply listed "Kindle for iOS" as the only supported platform.

The important change, however, comes in the second paragraph, where it now reads:
KF8 features are not currently supported in Kindle Edition with Audio/Video content.
It then goes on to specify that a mobi7 file must be delivered to Amazon with self-contained audio and video. These two factors are crucial to understand and be aware of. 

Firstly, and to my mind most importantly, KF8 does not support audio/video content. That is, only reflowable files can currently contain multimedia content, which fixed layouts are excluded. 

The phrasing of this statement is somewhat convoluted, and would have been much clearer in its intent had it read: Audio/Video content is not supported in KF8, rather than reversing this to state that KF8 features are not supported, as if it were the audio/video content that supports the format, and not the format that supports the content. But this, perhaps, is just an English major's nitpicking.

Secondly, the audio/video content must be self-contained (i.e. embedded), and therefore, streaming content is not supported in any case. This is almost certainly a move by Amazon to limit bandwidth use, since it provides this for free. There is no inherent reason why the referenced content source must be internal when connected to a network.

As I mentioned in the previous post, I have tried this and found it works quite well on my devices. The major obstacle for independent authors here, as with fixed layout files in general, will be the file size restrictions, since video can quickly increase your file size. A few short interviews or behind-the-scenes videos, however, should not consume too much space. Cloud Atlas, for example, comes in at only 10Mb with four short embedded videos.

Saturday, April 20, 2013

Kindle Comic Creator - An Analysis


Last week Amazon released the public version of its newest addition to the Kindle creation suite, the Kindle Comic Creator. KC2 is a graphic user interface that allows you to create KF8 fixed layout ebooks using a drag-and-drop approach, which makes it simple, fast, and - with a number of exceptions - efficient. And, of course, one it's best features is that it's completely free.

The first and most obvious caveat to point out is that KC2 will only create comics. That is, you can only create Kindle fixed layouts files that have the "comic" book-type. There is not even an option to change this: it is simply a built in feature of the program. This means there can be no live text functionality (dictionaries, search, etc.), no bookmarks, and in some cases, no hyperlinks or background image zoom (even though KC2 ironically embeds images using the <img src> insertion method, against the recommendations of the Kindle Publishing Guidelines). Refer to my Kindle Fixed Layout Functionality chart for specific details.

An equally important point to make, however, is that you can really only use Kindle Comic Creator to produce very simple layouts, with minimal formatting. KC2 provides a Rich Text Editor that only allows for basic text styling features such as bold, italics, and underlines, as well as changing text size and color. You can alter the line height, and the letter-spacing, and embed your own fonts - although the preview window will NOT show them, making accurate layout impossible (embedded fonts will appear on the compiled device, but not in the KC2 preview window). Moreover, you cannot change the alignment (all text is left-aligned) or add styles for headers and sections, making it less than adequate as a text creation tool. You can, however, add inline images for such things as drop caps or unsupported glyphs.

Several additional points should be made regarding claims stated in the User's Guide or on the KC2 page. A significant one that I've seen running through the Kindle Forums this week is the page spread issue. Amazon states that you can "create books with double page spreads or facing pages," and this is true with one huge exception: you can only do so when there is no region magnification present. That is, you must choose "No" to the question "Would you like to create Kindle Panel View" during the title setup process:
Note that this value cannot be changed once the title has been created. If you later change your mind, you'll have to start all over (or manually alter the settings in the OPF and re-import the title into KC2).

Also notice that on page 48 of the KCC User Guide, under Section 3.4 Joining Pages, the first line states explicitly (if not as boldly as it might) that the information that follows in that section applies only to ebooks "without Kindle Panel View" (my italics). This is the one and only place that this is mentioned! However, notice that these instructions for "Joining Pages" and using page spreads appear only in the User Guide in this section - Section 3 "Creating and Editing Books without Kindle Panel View" - while Section 2, which covers "Creating and Editing Books with Kindle Panels," does not contain any information regarding page spreads, because they are not available when Panel View is present.

Those who have referenced the Kindle Fixed Layout Functionality chart will know that this is the case with RegionMag in general when the "comic" book-type is chosen: page-spreads only work on the HD7 and Gen2 Fire, as well as the Android app, when RegionMag is absent, while on the HD8.9 and Paperwhite they work more or less correctly (see the chart footnotes for details). And, of course, two-page spreads do not work in any case on the Kindle for PC app or Kindle 3 (and I would guess the Kindle for Mac app as well).

Furthermore, you can only select "Unlocked" for the orientation value if you chose "No" to Panel View: which means any titles that have Panel View must be locked in either Portrait or Landscape orientation. This is a shortcoming of region magnification at present, which does not translate well from one orientation to the other when auto-orientation is allowed. Thus, Amazon have eliminated this option here.

As a final note on this subject, I should point out that page spreads do not work at all with any other book-type but comic, including (for some unfathomable reason) children's books! The only exception to this at present is the Paperwhite; even the HD8.9 no longer accepts two-page spreads in children's books, even though it did prior to the last update.

Another aspect of this that has been running through the Forum threads is that that orientation icons on the Display panel in KC2 will only show up when the "No" and "Unlocked" configuration is selected: in all other cases, these icons will be absent. 

In addition, the "Add Blank Page" option will only be available with this configuration. I have tested the functionality of the Layout-Blank value, which is added to the OPF Spine item in a somewhat different manner than described in the Kindle Publishing Guidelines. Here, KCC adds both the "facing-page" value along with the "layout-blank" as a single property:
<itemref idref="item-4" linear="yes" properties="facing-page-right layout-blank"/>
However, this makes the blank page function just like any other page that you might add, which shows up in both portrait and landscape orientation, rather than only in landscape as is supposed to be the case with the "layout-blank" value. In none of my extensive tests have I ever seen the layout-blank work as it should, with the sole exception of the Paperwhite when the "comic" book-type value is not chosen (i.e. it works correctly with the "children" book-type, or none entered). The only reason to add a blank page is so that it retains a two-page spread in landscape, rather than centering a stand-alone page, but if it's going to show the blank page in portrait orientation as well, there's absolutely no point in adding the "layout-blank" value: it's just another page at that point.

I also want to point out here that the inner margin issue is still present using KC2: that is, on every Kindle Fire model except the generation 1, and also on the Andoid app, when the "comic" book-type is chosen, the inner margin is removed from two-page spreads, regardless of whether you use the "facing-page" or "page-spread" Spine value: they are all treated as page-spreads, and "facing pages" simply do not exist.

Another point I'd like to make here is that, contrary to the claim made on page 34 of the KCC User Guide, ebooks made using KC2 do NOT appear on the Books tab of your Kindle device. Because KC2 uses Kindlegen for its conversion, the same reservations apply here as they do when doing any conversion through Kindlegen. In this case, the required EBOK value for the "CDE Type" is not added, and so the files produced will appear on the DOCS tab when side-loaded. Only when these files are uploaded and put on sale via KDP will the downloads appear on the Books tab.

Finally, I want to mention the two features that actually make this a reasonably useful tool, and these are the creation of Panels and the built-in HTML/CSS editor.

Kindle Comic Creator not only lets you create text and image pop-ups using a graphic interface to visually layout and adjust the individual panel size and placement, but it will do this automatically using an auto-detect feature that is very handy. And regardless of the method used, you can always alter and adjust them later, even after saving and reopening the project. My tests have shown that the auto-detect function works only when there are white spaces between panels, not black ones. The page in my Advanced Template that has five panels divided by black borders, for example, was seen as one panel using auto-detect. This may simply be due to a lack of contrast between panels, however, and some adjustment in the settings is available, although I have not tested them extensively. Also useful is the fact that you can also drag-and-drop the panel thumbnails to quickly change their reading order, which is rather handy. Ultimately, however, I found the manual panel creation process more cumbersome than helpful, and not useful at all for complex layouts. You cannot, for example, add a different image or fill to the zoom region, or change the formatting of the lightbox effect without resorting to manually modifying the code, which essentially undermines the entire point of the application.

On that note, however, the other feature I will mention here is that KC2 does boast a nice HTML/CSS editing feature that allows you to alter the underlying code from right inside the program. This could be its nicest feature, were the preview able to actually show the embedded fonts correctly. But instead it will only show your custom fonts as system defaults, for which you can set the one that is the closest as a "fallback" using a drop-down menu beside the embedded font in the Rich Test Editor. Unfortunately, previewing pages is a less than adequate experience, as far as accuracy is concerned, and I ended up having to continually export the KF8 converted file to an actual device so I could see what it really looked like. If you're only using simple fonts like Georgia or Tahoma, KC2 should suffice, but if you want to add in more artistic fonts like Marker Fine Point or Eraser you're out of luck.

Ultimately, Kindle Comic Creator might be useful as a way to set up your initial layout, before adjusting the underlying code by hand. But I still recommend you do most of your coding manually, unless you're building a title with very basic layouts. KC2 only adds a small amount of extraneous entries to your code - primarily kindle generator references (such as "data-app-amzn-ke-created-style") - all of which can be deleted during cleanup. For image-only pages it will also add the CSS styling to the HTML tags, which can be a nuisance, but nothing that can't be easily replaced. The main place where KC2 will prove most useful for many Kindle comic creators is in the placement of Panels, which will generate CSS positioning data that can then be massaged for optimal placement.