One little validation error -- forgiveable?

[JSWolf]

Originally Posted by DiapDealer

I would think that if you have no epub3-specific metadata needs, simply changing the package version in the OPF file would be enough to make it become an epub3.

There are some metdata changes and/or additions that need to go into the OPF header. Also, you need to build a NAV ToC that also has to go into the OPF. And finally there is the code needed for the audio both in the OPF and XML.

[Psymon]

Originally Posted by JSWolf

There are some metdata changes and/or additions that need to go into the OPF header. Also, you need to build a NAV ToC that also has to go into the OPF.

I gather that link I gave (in my last reply, and earlier here) basically "walks you through" what you need to change -- and that's basically it?

[eschwartz]

Originally Posted by Psymon

Plus I'm so happy with Sigil as my editor. I don't know how easy Calibre is for editing code -- is it comparable to Sigil, do you find (those of you who have used both)?

The main difference between Sigil and calibre editor, is that Sigil includes a Book View and calibre doesn't. That is not editing code though.

Additionally, calibre doesn't have a clips feature. (Yet?) I do not know how important that is for you personally, but it is a consideration for some.

(Oh, and of course, calibre allows you to choose the structure, rather than enforcing anything like Sigil does. The only changes are when you use an automatic tool like Fix HTML or Beautify, or add/remove/rename files when the manifest & OPF gets updated.)

[odedta]

Calibre has way more features and tools than Sigil and it is being maintained by an awesome team of developers led by Kovid Goyal.

Calibre does have a Book View, double click any book in your library...

[DiapDealer]

Originally Posted by odedta

Calibre does have a Book View, double click any book in your library...

Well that's a tiny bit disingenous. The difference is that Sigil lets you EDIT in its Book View. That was the point. I'm not taking sides in any silly X is "better" than Y debate--I use both at different times for different things. But eschwartz was correct: the difference is mainly Sigil's WYSIWYG Book View, and clips

[eschwartz]

Calibre has a book view, yes, but the editor does not.

Book View in Sigil is a WYSIWYG editing mode, differentiated from the Preview feature.
Both calibre editor and Sigil have a Preview and a Code View.
Only Sigil has a Book View.

Context is important, and we are not discussing the ebook-viewer.exe anyway.

[odedta]

What are these images if not an eBook viewer and editors?

Seriously... Sigil has a WYSIWYG editor which is a nice feature, however, what is the real difference if you can see the book and edit the code accordingly? if you use a WYSIWYG you probably won't have good compatibility for devices since Sigil is programmed to write specific code for each of the buttons. Meaning, Sigil is not made for making EPUB3 books and that's where Calibre comes in.

So if you put the two side by side, I'd choose Calibre any day!

[dgatwood]

Originally Posted by Psymon

Just as an experiment, I thought I'd add an audio (MP3) file to my ebook, to see if it would work, following Liz Castro's tutorial on how to do it (I even sprung a whopping $5 on her book about adding audio/video). Apparently audio and video only currently work in iPads and Nooks, but I can certainly attest that they do indeed work no problem in the former (I don't have a Nook, but I'll take her word for it).

The only problem is that adding in the <audio> tag gives my perfectly-valid ebook an error (or series of errors) related to that tag.

I think it might be possible in EPUB 2, but you're not going to like what you have to do. Take a look at this part of the spec:

2.3.1.2: Items That Are Out-Of-Line XML Islands


You can implement it like this:

1. Include two copies of the chapter—one copy with the audio tags specified as XHTML5 content, with media type text/html, and one without those tags, with the usual XHTML 1.1 media type.
2. In your OPF file, add an entry for both.
3. In the item entry for the HTML5 version, use the id attribute value from the XHTML version's item in the fallback attribute.
4. Set the required-namespace attribute to "http://www.w3.org/1999/xhtml".

With that change, you'll get warnings from the validator instead of errors. With that said, I have no idea whether real-world readers will use the HTML5 version or skip it and use the fallback.

You might also have better luck if you specify an empty CSS file in the fallback-style attribute.

[eschwartz]

Originally Posted by odedta

What are these images if not an eBook viewer and editors?

Seriously... Sigil has a WYSIWYG editor which is a nice feature, however, what is the real difference if you can see the book and edit the code accordingly? if you use a WYSIWYG you probably won't have good compatibility for devices since Sigil is programmed to write specific code for each of the buttons. Meaning, Sigil is not made for making EPUB3 books and that's where Calibre comes in.

So if you put the two side by side, I'd choose Calibre any day!

I totally agree, I prefer calibre too -- but it is worth mentioning that if someone DID feel the WYSIWYG editing was a crucial factor, then they should and would prefer Sigil.

Seems we all agree here, so, moving on...

[Psymon]

Okay, I just spent hours trying to convert my epub2 to epub3, using that guide that I mentioned earlier, i.e....

http://sketchytech.blogspot.ca/2014/...learnt-in.html

I got rather confused in parts, but eventually I think I figured things out, and then wanted to see if my book would validate. At 14 megs it's too big to upload to the online validator, and so I downloaded epubcheck to my computer and then went through the nightmare of getting that to run correctly (due to errors in getting java to be recognized).

FINALLY I got that figured out, too, but I ended up getting some errors that look like this...

S:/walden.epub/OEBPS/content.opf (-1,-1): Error while parsing file 'The prefix "opf" for attribute "opf:scheme" associated with an element type "dc:identifier" is not bound'.

I did a search for that, and I can't seem to find anything to tell me what that means -- I followed the steps at the above site exactly.

It's so easy to do epub2 files in Sigil -- I don't know if I'm cut out for all this exasperation for epub3 (all just for one audio file).

[dgatwood]

Originally Posted by Psymon

FINALLY I got that figured out, too, but I ended up getting some errors that look like this...

S:/walden.epub/OEBPS/content.opf (-1,-1): Error while parsing file 'The prefix "opf" for attribute "opf:scheme" associated with an element type "dc:identifier" is not bound'.

This means that somewhere in your opf file, you have an element whose tag name is <dc:identifier ...> that contains an attribute called opf:scheme, but you don't have an xmlns:opf="..." attribute on either that element or on one of its ancestors to tell the validator what the opf: prefix means.

[Psymon]

Originally Posted by dgatwood

This means that somewhere in your opf file, you have an element whose tag name is <dc:identifier ...> that contains an attribute called opf:scheme, but you don't have an xmlnspf="..." attribute on either that element or on one of its ancestors to tell the validator what the opf: prefix means.

Um, can you say that in English?

Sorry, I really don't understand.

[Psymon]

Originally Posted by dgatwood

you don't have an xmlnspf="..." attribute on either that element or on one of its ancestors to tell the validator what the opf: prefix means.

Okay, I did a search in my book for "xmlnspf", and there isn't a single instance of it anywhere, in any files, so I went back to that aforementioned guide on what to fix/change...

http://sketchytech.blogspot.ca/2014/...learnt-in.html

...and in there, one of the first things he says to change is this:

Change the opening metadata tag:

<metadata xmlnspf="http://www.idpf.org/2007/opf" xmlns:dc="http://purl.org/dc/elements/1.1/">

to:

<metadata xmlns:dc="http://purl.org/dc/elements/1.1/">

and with this required change all opf stuff seems to be out.

And I did that -- and so it would seem that he's saying to get rid of the "xmlnspf" reference.

However, in the next "thing to do" in that guide, he says:

Remove opf:scheme attribute from dc:identifier
<dc:identifier id="BookId" opf:scheme="UUID">urn:uuid:56ca9730-7e4a-446b-962b-74db6533d168</dc:identifier>

now looks like:

<dc:identifier id="uid">56ca9730-7e4a-446b-962b-74db6533d168</dc:identifier>

Notice that the value of the id attribute ("uid") in the dc:identifier tag pairs it with the attribute unique-identifier in the opening package tag, which has the same value.

I did what he says to the "BookId" item he shows, but do I remove any "opf:scheme" info from all other "dc:identifier" items? I'm a bit confused, because the next one that appears in my file is <dc:identifier opf:scheme="calibre">, which it would seem that Calibre inserted in there, not me.

And then the only other <dc:identifier> items that have "scheme" in them are these:

<dc:identifier xmlns:ns1="http://www.idpf.org/2007/opf" ns1:scheme="calibre">ab26fb4c-2009-488d-9299-5711d36d9663</dc:identifier>
<dc:identifier xmlns:ns2="http://www.idpf.org/2007/opf" ns2:scheme="ISBN">978-0-9680573-5-3</dc:identifier>

As usual, I'm confused.

[theducks]

Originally Posted by odedta

What are these images if not an eBook viewer and editors?

Seriously... Sigil has a WYSIWYG editor which is a nice feature, however, what is the real difference if you can see the book and edit the code accordingly? if you use a WYSIWYG you probably won't have good compatibility for devices since Sigil is programmed to write specific code for each of the buttons. Meaning, Sigil is not made for making EPUB3 books and that's where Calibre comes in.

So if you put the two side by side, I'd choose Calibre any day!

I leave/use Sigils Preview Pane on my upper Monitor.
Tou can't edit in the PV pane, but it will synch CV to the line if clicked. I aoid editing in BV like the plague. Just too many artifacts for my taste

[dgatwood]

Originally Posted by Psymon

I did what he says to the "BookId" item he shows, but do I remove any "opf:scheme" info from all other "dc:identifier" items? I'm a bit confused, because the next one that appears in my file is <dc:identifier opf:scheme="calibre">, which it would seem that Calibre inserted in there, not me.

Either remove the entire opf:scheme="calibre" attribute in every <dc:identifier ...> (scheme isn't a valid attribute for dc:identifier) or rewrite them as something like this:

<dc:identifer id="foo">...</dc:identifier>
<meta refines="#foo" property="identifier-type">calibre</meta>

At least I *think* that's the right syntax. It probably makes more sense to just nuke them all, though.

For the ISBNs, change it to:

    <dc:identifier id="isbn-id">urn:isbn:9780101010101</dc:identifier>
    <meta refines="#isbn-id" property="identifier-type" scheme="onix:codelist5">15</meta>

replacing 9780101010101 with the actual ISBN. Also, if it isn't an ISBN-13, change the number 15 to the appropriate value for your ISBN type from this list:

http://www.stison.com/onix/codelists...codelist-5.htm