3 ms·
Unless you made a mistake when copying, "<ol><li></ol>" is not valid XHTML. The li tag is not closed. It would be valid HTML though. "<ol><li></li></ol>" or "<
by bhaak 6y ago
Unless you made a mistake when copying, "<ol><li></ol>" is not valid XHTML. The li tag is not closed. It would be valid HTML though.
"<ol><li></li></ol>" or "<ol><li/></ol>" would be valid XHTML.
- davidgerard 6y agoyeah, I was writing it short-form for the blog, sorry. The actual XHTML in the ePub is valid, and goes something like: <ol class="list_"> <li id="id_RefHeading___Toc28800_897132658" value="2" class="block_10"><b class="calibre5">Introduction: Taking over the money</b></li> </ol> The thing that's disconcerting me is that so far I've had zero responses that are "you should use this tool instead to get from LO to an ePub that passes epubcheck, you foolish person." Like, not even LO’s internal ePub export passes epubcheck. I thought this would be a sufficient nerdbait ...
- bhaak 6y agoWord processors are notorious for creating convoluted structures. I wouldn't be surprised if the lists in the headings are due to the internal structure of LO not being easily mapped to the structure of a DOCX. Feels like a workaround for some specific issue. As I said previously, pandoc might be worth a look. But it's installation is more involved and it's able to convert everything to almost everything (it would even allow converting a LaTeX document to ePub :-) https://pandoc.org/epub.html https://pandoc.org/epub.html). But I can't really attest the quality for more complex documents. You have a working workflow and sometimes it's better to keep the devil you know instead of getting lots of unknown devils.
- davidgerard 6y agojust tried pandoc 2.5 (from Ubuntu 20.04), and it did an okay job but with the complex bits failing. And the output fails epubcheck %-D