TOC Wonkiness

[Hitch]

Hi:

First, let me say I really love Sigil--thanks for making it.

I'm in the middle of converting a lousily-formatted epub that was InDesign-generated (by someone else) into an epub viable for Nook and which I'll then run thru Calibre to generate a .mobi for Amazon. I've run through the originally-provided epub and inserted chapter breaks, fixed the images, and so forth. However, weirdly, the last two H1's I inserted, for an "About the Authors" page and an "Other books in this series" page don't work in Nook, although all the other TOC pointers, all of which are xhtml formatted exactly the same, DO work in Nook. Suffice it to say, it's a little frustrating.

I can't see anything, html-wise, that would be causing this wee glitch. Does anyone have any thoughts about this?

Thanks,

Hitch

[Valloric]

It could be a bug, or it could be nook weirdness. Either way, you still need to create a new issue on the tracker with the epub file attached. See this wiki page.

[Hitch]

Originally Posted by Valloric

It could be a bug, or it could be nook weirdness. Either way, you still need to create a new issue on the tracker with the epub file attached. See this wiki page.

Hi, Valloric:

Thank you for your reply, but I cannot do that. The content of the epub file does not belong to me and I cannot publish it. I can certainly create a new issue on the tracker, but I can't upload the file. BTW, it's not actually the Nook; it's B&N's e-Reader for PC; I misspoke when I referred to it as "Nook on PC."

I'm at the point of giving up, anyway. I think this might have something to do with the extensive stylesheets used by InDesign, but although I can muddle about pretty effectively in html, my css is weak at best and frankly it's like the paper-designer deliberately tried to make my life a misery for the digital conversion. I've repeatedly re-created the chapter titles so that the ones that don't work match the ones that do, coding-wise, but every time I upload this sucker to the B&N e-reader (to proof it before converting it to .mobi), different chapter headings stop working. It's driving me to drink.

Thanks anyway--if anyone has a better e-reader that utilizes TOC that I could use to "proof" my content prior to conversion, I'd certainly welcome THAT suggestion, this B&N e-Reader is a total POS, you can't even delete uploaded files (I kid thee not).

Hitch

[Firepong]

Try <h1 class="calibre3" id="heading_id_3"><a class="calibre4" id="About_the_Authors" name="About_the_Authors"></a>About_the_Authors</h1>

If that doesn't work, switch <h1 class= to <h3 class= and </h1> to </h3>.

If it does work, just point your ToC to the id in that line of code.

If this doesn't work on the Nook, might be the way they handle things. I know I've ran into a couple codes that will not work on the IPad iBook's app.

P.S. You might have to change the font settings and things in there. Thats just my universal settings for things like that.

[charleski]

The easiest thing is to unzip the epub and upload the toc.ncx file that Sigil will have created. That won't contain any copyrighted information, just the names of the chapters, but will allow people to check if there's something wrong with the toc creation or whether the fault lies with the nook.

[Valloric]

Originally Posted by Hitch

Thank you for your reply, but I cannot do that. The content of the epub file does not belong to me and I cannot publish it. I can certainly create a new issue on the tracker, but I can't upload the file.

As the linked wiki page mentions, you can add a "Private" label to your issue on creation and only you and I will be able to see it. It will not be publicly available in any form. Lots of publishers do just this, to the point that the number of non-public issues on the tracker is... substantial.

[Hitch]

Originally Posted by Firepong

Try <h1 class="calibre3" id="heading_id_3"><a class="calibre4" id="About_the_Authors" name="About_the_Authors"></a>About_the_Authors</h1>

If that doesn't work, switch <h1 class= to <h3 class= and </h1> to </h3>.

If it does work, just point your ToC to the id in that line of code.

If this doesn't work on the Nook, might be the way they handle things. I know I've ran into a couple codes that will not work on the IPad iBook's app.

P.S. You might have to change the font settings and things in there. Thats just my universal settings for things like that.

Hi, Firepong:

Thanks, I actually tried that, switching the non-chapter headers to other header types, but no joy. I'm having problems with the converted version (to .mobi) as well, so it's the doc, it's not the B&N e-reader (n.b. - unbelievably, you cannot delete uploaded personal content from your B&N e-reader without--are you ready for this?--not only manually deleting the file from your PC's directories, but UNinstalling and REinstalling the B&N e-reader. Unbelievable. This is the answer that their CSR gave me, I almost spewed my Starbucks over that one. You've all been warned! ).

@Valloric: I'll upload the file later today with an issue tracking memo. Thanks! In the interim, I'm just uploading the whole mess (orig. epub) to Sigil again with a different file name, Ctrl-A it, copy it into my html editor and delete all the garbage, then see what happens. I know I can use Sigil's html editor (what html editor product is that, anyway? I really like it), but the sections are starting to make my brain hurt, I guess I should have built the TOC first...well, that doesn't work anyway. Bugger. Ah, well...the joys of converting someone else's InDesign garbage is enough to make my head explode!

Thanks all for your input, I'll keep you posted if I figure out what the heck it is,

Hitch

[Sabardeyn]

Ok, maybe I'm nuts... but I noticed that the two affected files, if you named them the same as posted above, have spaces in them. Are you using the most up to date version of Sigil? Perhaps this is the space bug (or a variant) that was resolved in the previous version?

[Valloric]

Originally Posted by Sabardeyn

Perhaps this is the space bug (or a variant) that was resolved in the previous version?

The spaces bug is fixed in 0.2.0beta3, not for Sigil 0.1.9.

[Sabardeyn]

I noticed that Hitch did not mention the version he was using in the original post. Despite this potential snag, I assumed that he might have the current version, and discovered one of those bugs that was thought to have been resolved and is not.

(BTW, thanks for the clarification Valloric. When updating, I tend to run almost one update behind. So I am frequently unsure which version I'm using at a particular time.)

[Hitch]

Originally Posted by Sabardeyn

I noticed that Hitch did not mention the version he was using in the original post. Despite this potential snag, I assumed that he might have the current version, and discovered one of those bugs that was thought to have been resolved and is not.

(BTW, thanks for the clarification Valloric. When updating, I tend to run almost one update behind. So I am frequently unsure which version I'm using at a particular time.)

Sabardeyn:

I saw your original post--in which you said

but I noticed that the two affected files, if you named them the same as posted above, have spaces in them.

However, as I had not in any way, manner, shape or form named the "two affected files," I really wasn't quite sure what it was to which you were referring; I'd not indicated filenames at all, merely that my epub's TOC wasn't working in B&N's desktop e-reader. So sorry to have not gotten back to you. Valloric has kindly looked at the files in question, and as near as he can tell, everything is in its correct place, so we think it's a bug or glitch with B&N's desktop e-reader (which I have now nuked as my epub test platform due to the other problems I mentioned in this thread, ANYWAY.)

I'm looking forward to using Sigil this weekend, as a matter of fact, for yet another conversion. Lovely program, and I am particularly enamored of the ability to use images as links back to the TOC, smashing.

Thanks,

Hitch