Quote:
Originally Posted by Notjohn
I originally built my ebooks as a single html file (zipped with images if there were any) so I regularly used the # in links. When I switched to Sigil-built epub, what Tex describes here is exactly the way it worked (and continues to work) for me.
|
Yeah, I swear that's how split worked for all the years I've used split.
youcantoo or Notjohn, do you attach an actual EPUB that actually recreates OP's issue?
I tested on a few of my latest books, and the split code works exactly like KevinH said. And it leaves me scratching my head, because I
know I've seen the OP's issue many times over the years. (Although I just throw away all link code and recreate clean links on my own, so it never really bothered me.)
(I'm going to dig through some of my EPUBs and see if I can get a good testcase. And I'll definitely keep my eye out on this in the future.)
Quote:
Originally Posted by KevinH
So the test case presented to us is somehow suspect. In fact the presence of a unclosed br tag in the test case and li tags not inside an ol lead me to believe that the structure of the original html file was quite broken (or was broken when extracted) but still an unclosed br is not valid xhtml.
|
Could be, could be...
I know Finereader sometimes creates some poor code (and maybe this is when I'm splitting files and seeing the error, when it's still in an invalid state).