I finally got my converted book to look ok in epub2 and went on to try EPUB3.
I got errors! I am not sure how many because the tools only tell you about the first, but I saw several others in the HTML
Attached are three images: The input, The error message, the actual html.
The html error is that there is an ending tag and no beginning one. I see this on each item in the list.
I did some more testing and removing all formatting and links in this selection makes the error go away. This isn’t surprising. But considering that the Heading 2 above this section is correctly ended, I don’t know why the extra ending are coming from.
Boy-oh-boy is it great to have a nice and simple single CSS stylesheet with EPUB3 — THANKS
I moved the text to a test page at the front of the book and tried several things:
Removing the links didn’t help
Making the em-dashes consistent didn’t help. They had been a mix of en-dashes and em-dashes with and without spaces before.
Undoing and re-doing the list didn’t help
Undoing the list did help!!!
Of course, I have a couple of dozen other lists that work just fine - so good luck finding the source of the bug.
It does compile as a KF8 and can be viewed with Calibre and Kindle Previewer 3 (very slowly) without error.
BTW it looks Better as an EPUB3 than it does as KF8.
I removed the problem text for the time being and recompiled. This is the only compile error in a text that is 170 8.5x11" pages has 50+ images/figures and lots of lists & links.
I can send you my test file if that will help. BTW how do I extract a single document from the binder and send it?
David, can you try to make a minimal test case Scrivener Project that reproduces this potential bug then zip it up and attach it here? Without a test case it is impossible to get any further.
If the malformed HTML is reproducible, you could send it to L&L support directly with a link to this thread, or if you want confirmation from another user before that then use something like workupload.com/
I think I understand what is going. There is something really weird in the styles for that document. I have simplified it to only 2 list items. I remove the list formatting, and make sure the text is “No Style”, then I make it a bulleted list and the text becomes “Heading 1” style (but does NOT look like Heading 1 style (bold etc.), visually it is still No Style). If I select the text in one list item and try to unset the style (NoStyle via ⌘⌥0), then it looks like Heading 1. Then I have to unset it again.
When the text is in this indeterminate state (says Heading 1 but looks No Style), then the HTML corruption occurs. The compile format also has a Heading 1 style which is centered and why the HTML seems to get mangled.
I’ve made a simpler test case from yours with screenshots showing what happened.
Keith: any ideas what is going on? The second list item in the test case (“EPUB3 Bug” doc text starts Manuale) says it is Heading 1 when it isn’t, and this seems to cause output HTML errors… V3Bug2.zip (164 KB)
I can confirm the HTML output errors are fixed, thanks Keith! The style problem in the editor persists in V3.0.1. I made a screencast demonstrating the issue. The list item claims it is “Heading 1” when it isn’t (visually). Setting it to “No Style” paradoxically makes it look like Heading 1 and you cannot use “No style” again, it doesn’t work. You have to remove the list, then set “No Style”, then redo the list:
There’s nothing wrong with a paragraph having a style associated with it even if it looks nothing like that style. If you apply a style and then change the formatting of the paragraph, the style will remain (just as it does in Word etc).
To remove a style from a paragraph, you either need to click into the paragraph with no selection, or select the whole paragraph. In the video you were not selecting the whole paragraph (because you did not select the bullet). If it didn’t work like this, there would be no way to clear character styles without also clearing paragraph styles.
Yes this all makes sense. I normally use Pandoc lists for my writing and the only RTF like lists I use are Word lists where you cannot select the bullet, and this was where I was going wrong. Thanks Keith!