Quote:
Originally Posted by st_albert
But don't forget that will regenerate the toc.ncx based on the <hx> tags it finds. If you've customized toc.ncx in Sigil-0.4.0 it will be gone.
|
Fortuitously, I'm a form->follows->structure kind of bookmaker, and I insist my Crews do that as well; we don't use headers as "cheat" mechanisms solely for formatting, and we don't use non-structural items for chapter heads, (or tables of illustration, etc.), either. Unlike FAR too many people, I don't put TOC entries willy-nilly; I use headers for structure and for TOC's.
Although it seems that user_none/JS has resolved it, anyway. Happy day.
Now, if he could just blow up whatever moron at B&N that thought that "hyphenation" meant "break a word wherever you run out of room," instead of "break a word at Syllables," that would be spiffy. I wasted more than 7 hours of my own time, and (I don't have the tally yet of) my Crews' time this week screwing around with trying to get headers with faux-smallcaps and Raised Initial (so--headers with multiple spans inside the h tags) to work on a Nook, and I nearly threw the bloody thing out the window. We tried it all; we tried adobe-hyphenate: none; we tried the optimize-speed setting; I consulted with Joshua about it...we can make it not-hyphenate on any plain header; but the moment you add multiple spans inside the h tags, it either wraps after almost every word, so you end up with a vertical column, OR it doesn't wrap at all, so the header runs off the right-hand edge of the screen (oh, joy), OR, it just places the words in the header willy-nilly all over the page.
Again...didn't mean to hijack this thread, and I know I should go rant about it in the epub forum, rather than here, as the Sigil forum answers too many basic html & css questions anyway (rather than Sigil-related), but I rather prefer my peeps here; if ANYONE has worked out a trick on this, please let me know, thanks.
Best,
Hitch