Quote:
Originally Posted by meme
The lack of the save warning is an issue and I can duplicate it - thanks, we'll look into correcting this (and the same issue with Link Stylesheets).
|
No prob.
Quote:
|
As for lists - what do you use, just indented paragraphs? (I assume that's what calibre uses when converting). I'm open to changing the format of the file (and even changing it to toc.xhtml) - this was just a first version to get feedback.
|
I use indented paragraphs, but I'd make sure you get a pretty solid consensus before changing... I can be an odd bird.
I've just found that it's easier for me to get a stylistic consistency across a variety of renderers by simply using a handful of <p> classes and some very simple css. Styling list elements (especially nested) to look comparable in various apps/devices always seems to get a little hairy and frustrating for me. Plus I've just never really seen the advantage of ordered/unordered html lists for static content. *shrugs*
Also... the only time I usually even bother with an inline ToC is when I'm going to be building a MOBI from the ePub as well... and less is best when feeding Kindlegen (not that
that's a Sigil concern or anything), so I try to stick to <p>s and <blockquote>s so it doesn't get too complicated.
Like I said; just getting the text and the hrefs of an inline ToC built automatically from the headings is going to save me scads of time... however it ultimately works out.