Quote:
Originally Posted by LukeA
Copying and pasting in Sigil copies ids as well as everything else. If you are in book view you won't know this - it is only obvious in code view. I've found that just fiddling with paragraphs can result in duplicate ids across successive paragraphs without copying.
It seems to me that if duplicate ids are forbidden, Sigil should be smart enough to not create duplicate ids automatically - when copying, it should generate a new id for the pasted item. Ditto for generating multiple paragraphs out of one.
|
+1! LukeA beat me to it. I was about to say, some noob created a paragraph style, in CV (Code View), and without thinking, switched over to BookView and
started typing by hitting "enter" and typing merrily on, or cutting and pasting paragraphs (probably from a PDF, heavens help us, if not Word) into BV. Sigil did what it is supposed to do; it duplicated the previous paragraph style and class. Thus, you have tens of thousands of paragraphs with an id present. This is what happens when a DIY'er reads some posting on the KDP forum and decides to use Sigil like a word-processor. Fortuitously, you can simply regex that out, and the ePUB should pass validation--assuming everything else is fine.
Given how basic that error is, though, I wouldn't count on not finding other mistakes just as basic and just as painful.
Quote:
|
It seems to me that if duplicate ids are forbidden, Sigil should be smart enough to not create duplicate ids automatically - when copying, it should generate a new id for the pasted item. Ditto for generating multiple paragraphs out of one.
|
Don't see why, and I'd say, not necessarily. Do you seriously think that Sigil should have generated thousands of new id's for the thousands of paragraphs in that ePUB of 600 printed pages? Crap, I'd rather regex 10,000 identical id's than 10,00 different ones had I made that mistake (and don't think that I didn't make one that dumb, a long time ago). ;-) Sigil's not a word-processor; it assumes that its users are smart enough to know HTML, XHTML and CSS. {smile}.
Hitch