08-02-2012, 07:16 PM | #1 |
Junior Member
Posts: 1
Karma: 10
Join Date: Aug 2012
Location: Berkeley, CA
Device: none
|
validation error help in lay terms
Hello Sigilers,
Please help this inexperienced Sigil editor who has very little knowledge of HTML with this validation error: "The <reference> element's "type" attribute has value "copyright" which is not an OPF-specified value. Either use a predefined type or start your type with "other."." I'm trying to correct epubs that were created by a conversion company. I'm starting to suspect that the validation errors I'm finding when using Sigil are caused by the conversion company. Any help would be much appreciated. |
08-02-2012, 07:21 PM | #2 |
Resident Curmudgeon
Posts: 74,048
Karma: 129333562
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Change where it says Copyright to Copyright-Page.
|
Advert | |
|
08-02-2012, 08:57 PM | #3 |
Bookmaker & Cat Slave
Posts: 11,462
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
...and your conversion company is in India. ;-) It's a common error with Indian-made ePUBs. I don't know why, but naming the guide items correctly seems to be a huge issue with them. Look for other odd naming conventions; and check their naming conventions against this: http://idpf.org/epub/20/spec/OPF_2.0...htm#Section2.6 to cover your butt.
HTH, Hitch |
08-02-2012, 09:06 PM | #4 | |
Resident Curmudgeon
Posts: 74,048
Karma: 129333562
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
|
|
08-02-2012, 09:43 PM | #5 | ||
Bookmaker & Cat Slave
Posts: 11,462
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
Although I know that this is your personal pet peeve, I have to tell you that now that Amazon accepts ePUB as source material, you will be seeing more and more of it. We provide conversion for publishers and aggregators, and they neither like nor want dual books; they want a single ePUB that meets both ePUB and MOBI standards. In order to provide an ePUB that meets MOBI standards when converted, you have to have an HTML TOC linked via the Guide; and as it is in its own file, like any other section, we do put the TOC in the NCX, ourselves. Moreover--before you start--I'd note that the 2.01 OPF Spec lists a TOC entry, and that's NOT for the NCX, as we all know. It's for an internal, HTML TOC. Clearly, the existence of an HTML TOC is not merely contemplated by spec but supported. AND, on top of all that, the ePUB3.0 working document states: Quote:
So you can call them--or me, for that matter--"idiots" all you want, but while you may have the luxury of making ePUBs precisely as you like them, for your own use, not everyone has that privilege. My company has to make ePUBs that meet the spec, and work on platforms like Apple (which uses the HTML TOC--NOT the ncx, at all, mind you). I have to make books for people that, quite reasonably, want ONE book that they can upload everywhere. So do the Indians, I'd imagine. I personally prefer only using the NCX--but my iPad doesn't support that. My Nook does. My Kindle Fire doesn't, but is moving toward it, and my K2 doesn't at all, obviously. It's clear from the 3.0 Working Group that we are moving TO a more-functional, defined "HTML TOC" that works somewhat like an NCX--in other words, is both human- and machine-readable, which is the current "glitch" in the proceedings. I mean, really--not to sound ever-so-slightly-exasperated, but why don't you go volunteer with the IDPF working groups and take it up WITH THEM? Everyone here knows all too well how you feel about HTML TOCs, and quite honestly, it's a bit RABID for something so minor. For the love of heaven, if you don't LIKE an HTML TOC, don't USE IT. In the interim, while you go sort them out and put them in their places, if you would, please, I will just shlub along here and do what my clients pay me to do. WITH the satanic HTML TOC's, if that's what they want. Affectionately, really, Hitch |
||
Advert | |
|
08-02-2012, 09:53 PM | #6 |
Resident Curmudgeon
Posts: 74,048
Karma: 129333562
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
The issue is that the internal ToC (of an ePub) currently is useless. There's no easy way to get to it. The NCX has an easy way to get to it. But why would we then want to go from the NCX to an internal ToC. We only need one ToC as long as there is an easy way to get to it. It doesn't matter if it is internal or external as long as it's just one and there is an external link to get to it.
|
08-02-2012, 10:09 PM | #7 | |
Well trained by Cats
Posts: 29,820
Karma: 54830978
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
|
Quote:
Chapter 1 "He was a cold and Stormy Knight" Not the styled text that is not allowed in the NCX, Multi-line (per chapter) TOC ... Once again, your personal tastes don't rule what others might want (OMG they put a pink Bidet in the TOC ) |
|
08-02-2012, 10:14 PM | #8 |
Resident Curmudgeon
Posts: 74,048
Karma: 129333562
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
But to get to that ToC, you have to go to the NCX and then if there is a Contents link, then you can go there. Otherwise, it's not easy to get to the internal ToC. Most eBooks I've read, the internal ToC adds nothing that I'm not already getting from the NCX.
|
08-02-2012, 11:43 PM | #9 | |
Grand Sorcerer
Posts: 27,553
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Quote:
Let. It. Go. ...woosah... |
|
08-03-2012, 12:04 AM | #10 |
Well trained by Cats
Posts: 29,820
Karma: 54830978
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
|
Which is why I put it at the END. It is there for those who must have it that way, but I can simply stop at the end of the story
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Free (Kindle KDP) Oh Lay and Story Minute sampler by Carol Lay [Newspaper Comics] | ATDrake | Deals and Resources (No Self-Promotion or Affiliate Links) | 4 | 03-18-2012 10:46 AM |
Validation Error | Adjust | ePub | 3 | 07-21-2011 12:06 AM |
Validation error | soparch | ePub | 2 | 04-15-2011 01:09 PM |
Error during validation | macdafydd | ePub | 19 | 12-01-2010 06:07 PM |
Validation error | rrosenwald | Calibre | 10 | 10-01-2010 11:12 AM |