Quote:
Originally Posted by DiapDealer
When I create a new html toc (nothing to be overwritten) both the <?xml version....>and <!DOCTYPE....> are both written to the same line as well.
So I don't think it's the overwriting that's the problem. It's the creation of the html toc code period. And like Kevin mentioned, this has probably been around forever. It's just that most people used pretty print at some point (which fixed it). You're only noticing it because of a) the cursor bug, and b) the existing toc that already had those two elements on different lines for you to compare to.
Start with an empty epub and create an html toc. You'll see the the <?xml version....>and <!DOCTYPE....> on the same line. It's been that way for a long time.
|
I see what you mean. That's something I never did before.
All my work has a Contents page before converting to epub. And if I edit a text page with a new header, I update the htmlToC manually in Code View - never been a problem. I noticed it this time because I was explaining to someone who wasn't happy editing directly in Code View.
From Kevin and Becky's posts, it looks like that won't happen in future. No more misalignment between Preview and Code View. I was more worried about Mac giving the impression that Sigil had stalled.