Quote:
Originally Posted by RootlessAgrarian
I tip my hat to your self-restraint :-)
|
One of the benefits of being awake for 24+ hours: you find it hard to get angry.
Quote:
Originally Posted by RootlessAgrarian
if it is a broken file, then what would be nice would be for Sigil to complain about the offending syntax rather than just sulk :-)
|
And again, I agree with you. Long-term plans include writing an epubcheck equivalent in C++ (with some more bells and whistles) and plugging that as a library into Sigil. That would then do the complaining: the user would be warned about the errors and asked whether he wants to proceed. Same thing for export.
But Sigil currently includes HTML Tidy and runs it on your HTML files before loading them. This
usually fixes any problems, but it's not perfect.
Quote:
Originally Posted by RootlessAgrarian
what I'd really like to know is how toc.ncx gets generated... whether Sigil is supposed to do that based on h1 and h2 tags in the xhtml files, or whether Sigil needs some external agent to generate toc.ncx before it can navigate the toc correctly.
|
Sigil uses the heading tags, yes. H1 through H6. It usually works well. I plan on enabling direct NCX and OPF editing some time in the near future ("near" means more than a month... let's say two).
You should really attach that epub file of yours on a new issue on the tracker. The more bug reports I get, the more bug fixes I can implement. EDIT: I see you added it to a post. That's a step in the right direction, but I prefer having it on the tracker. It means I can easily search for it later and watch for regressions.
Quote:
Originally Posted by RootlessAgrarian
I'll prowl the wiki when I have some leisure time and do a little more self-education.
|
Sadly, there's not much there. User documentation is non-existent. Some have lately offered to write it, but I said to hold off until 0.2.0 ships. I don't want people going through the trouble of writing docs that will become obsolete in about two weeks.