This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Validation errors with AZW and EPUB

Tags: None
(comma "," separated)
User avatar
KazAugustin
Registered Member
Posts
4
Karma
0

Validation errors with AZW and EPUB

Tue Nov 26, 2013 4:52 am
All the new features are really lovely but, before anything else, I'd dearly like it if the validation to formats actually, you know, worked. I am currently using Calligra Words 2.7.4 on KDE 4.11.3

EPUB: I am getting the following error when I validate with the idpf epub validator after exporting an exceedingly simple text document (not even a single page break!) to "electronic book document" format

Code: Select all
Type: ERROR
File: OEBPS/toc.ncx
Line:   14
Position: 11
Message: element "navMap" incomplete; missing required element "navPoint"


This is easy enough to fix through Sigil but then, why use Author if I have to correct later with Sigil? Also, for any budding ebook authors out there, many etailers will not stock your book if it doesn't pass the idpf validator, so this is a rather important obstacle.

Mobi: You keep saying "Mobi" but, of course, the Export function exports an .AZW file, which is slightly different to Mobi and is unreadable in the Mobipocket Reader. So let's be a bit precise about this. Author is supposed to export to "Kindle" format (.AZW), not Mobi (.PRC).

In order to test this out, using the same exceedingly simple document, I downloaded and installed Kindle Reader for PC on my Windoze machine. Kindle crashes each time I attempt to open the file. Relevant crash info is:

Code: Select all
Problem Event Name:   APPCRASH
  Application Name:   Kindle.exe
  Application Version:   1.10.6.40500
  Application Timestamp:   51a2d922
  Fault Module Name:   Kindle.exe
  Fault Module Version:   1.10.6.40500
  Fault Module Timestamp:   51a2d922
  Exception Code:   c0000005
  Exception Offset:   00301115
  OS Version:   6.1.7601.2.1.0.256.48
  Locale ID:   1033
  Additional Information 1:   0a9e
  Additional Information 2:   0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:   0a9e
  Additional Information 4:   0a9e372d3b4ad19135b953a78882e789


May I suggest that before we put in fancy word counts or EPUB3 compatibility, the basic issue of successful initial format export is solved first?

Yours in old-woman, ex-coder tetchiness,
Kaz Augustin


Bookmarks



Who is online

Registered users: bartoloni, Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]