Hidden headings/links don't work in iBooks?

[Psymon]

Originally Posted by Jellby

Mind you, neither "visibility" nor "overflow" are in the required CSS set for ePub 2.0.1, so there could be a spec-compliant reader which ignores them both, and then your h2 would be visible.

Oh, that would suck, if that happened. Is there any other, alternative way of accomplishing what I'm trying to do here?

[Hitch]

Originally Posted by Psymon

Oh, that would suck, if that happened. Is there any other, alternative way of accomplishing what I'm trying to do here?

Is there some reason you're not just using an empty header, with the alt attribute used to create a matching NCX/TOC item in Sigil? Instead of all the hidden this and that? is it because you don't want to repeat the text, in terms of the work, or...?

Hitch

[Psymon]

Originally Posted by Hitch

Is there some reason you're not just using an empty header, with the alt attribute used to create a matching NCX/TOC item in Sigil? Instead of all the hidden this and that? is it because you don't want to repeat the text, in terms of the work, or...?

Because I'm incredibly stupid, that's why -- seriously, I honestly can't believe that never occurred to me! I haven't tested it out in ADE or iBooks yet, but just in Sigil it seems to have done the trick, and, as you say, is pretty much all I needed to do.

I really can't think of why that never occurred to me -- it seems so simple and obvious!

I do have on question, though, regarding that. I wanted all the various poems to show up in the ToC as they do in the original book, with curly quotes around them. Within the title attribute within the <h2> tag, is there any issues that anyone knows of with having curly quotes within the regular quotes for that title attribute? Like, this is kinda what I end up with (for example)...

<h2 class="hidhead" id="respectable" title="“The respectable folks”"></h2>

In the title attribute, I've got basically two sets of quotes -- one curly, one regular. Should I be using character entities instead there? Or is it fine like that?

Thanks, Hitch -- for making me feel so stupid! Seriously, thank you for that!

[Hitch]

Originally Posted by Psymon

Because I'm incredibly stupid, that's why -- seriously, I honestly can't believe that never occurred to me! I haven't tested it out in ADE or iBooks yet, but just in Sigil it seems to have done the trick, and, as you say, is pretty much all I needed to do.

I really can't think of why that never occurred to me -- it seems so simple and obvious!

I do have on question, though, regarding that. I wanted all the various poems to show up in the ToC as they do in the original book, with curly quotes around them. Within the title attribute within the <h2> tag, is there any issues that anyone knows of with having curly quotes within the regular quotes for that title attribute? Like, this is kinda what I end up with (for example)...

<h2 class="hidhead" id="respectable" title="“The respectable folks”"></h2>

In the title attribute, I've got basically two sets of quotes -- one curly, one regular. Should I be using character entities instead there? Or is it fine like that?

Thanks, Hitch -- for making me feel so stupid! Seriously, thank you for that!

It's all right--it's one of the first Sigil tricks I learned. Only works auto-magically in Sigil, mind you. It saves our bacon regularly for things like..."Dedication" "Epigraph," etc.--pages where you mayn't want an actual "chapter title" but want it on the NCX. As far as the curlies, I'd have to go look myself to remember if there are any issues.

Hitch

[Psymon]

Originally Posted by Hitch

It's all right--it's one of the first Sigil tricks I learned. Only works auto-magically in Sigil, mind you. It saves our bacon regularly for things like..."Dedication" "Epigraph," etc.--pages where you mayn't want an actual "chapter title" but want it on the NCX.

I still can't believe I didn't just think of your solution on my own -- even worse, I can't believe Jellby didn't think of it! Ha ha

As far as the curlies, I'd have to go look myself to remember if there are any issues.

That would be great, if it's not too much trouble (assuming you did come across this scenario before). Thanks, Hitch!

[Jellby]

Originally Posted by Psymon

I still can't believe I didn't just think of your solution on my own -- even worse, I can't believe Jellby didn't think of it! Ha ha

He he, I did at some point . You'd still have the problem that it would take space, and some renderers are too eager to discard empty tags, so you may have to add a &nbsp; inside. That's why I didn't suggest it at first (when the problem was the spacing), and then just forgot about it.

[Psymon]

Originally Posted by Jellby

You'd still have the problem that it would take space, and some renderers are too eager to discard empty tags, so you may have to add a &nbsp; inside. That's why I didn't suggest it at first (when the problem was the spacing), and then just forgot about it.

Well, if that was the case, though, then I might as well just do it the way that we/you came up with before -- I mean, if I'm going to put an &nbsp; in there, then I might as well just put the text itsef (and skip the "title" attribute), right?

[Jellby]

It works, there's no practical difference, but if some renderer does not obey "visibility" or "overflow", the difference is that the &nbsp; will still be invisible, while the text won't.

Anyway, my preferred solution is to add the "id" to the <p> or <div> and completely removed the <h2>. That's perfectly OK with the final book, but it will break Sigil's automatic TOC generation.

[Psymon]

Originally Posted by Jellby

Anyway, my preferred solution is to add the "id" to the <p> or <div> and completely removed the <h2>. That's perfectly OK with the final book, but it will break Sigil's automatic TOC generation.

Yeah, I suppose I could do that, but there's about 50 poems that are listed in the ToC, and I'd hate to have a reason to run Sigil's auto thingie again come up, and then have to re-do it all manually -- on the other hand, though, as it is I do have to go back and manually change each and every one of those headings/links, and so maybe I can just leave that for the very last thing to do (and just hope that I remember to do so, at the end!).

Thanks! Thanks everybody, that is -- I might just leave this for now, work on other things that still need doing, and backburner those headings. And hopefully remember later.

[Psymon]

Originally Posted by Jellby

It works, there's no practical difference, but if some renderer does not obey "visibility" or "overflow", the difference is that the &nbsp; will still be invisible, while the text won't.

I was thinking about this, what you wrote earlier, that hiding (or not displaying -- however you want to word it, and code it) may not display in "some" devices. Do you know what devices that might be? I mean, if it was only going to "break" in, like 5% of the devices (or apps) out there, and then the worst that happens is that there's a bit more space inserted between the poem and the text before it (little more than as though there were an extra blank line in there), well, that's no big deal. If it works just fine the vast majority of the time, then I can certainly live with that.

[Jellby]

I have no idea, sorry. But to me, that the links don't work in iBooks is no big deal, to start with

[Psymon]

Originally Posted by Jellby

I have no idea, sorry. But to me, that the links don't work in iBooks is no big deal, to start with

Hardy har har

[JSWolf]

Originally Posted by Psymon

Hardy har har

One of these days Alice. Pow! Right to the moon.

To be honest, iBooks really doesn't matter as it makes up a very very small part of the eBook market.

[Psymon]

Originally Posted by JSWolf

To be honest, iBooks really doesn't matter as it makes up a very very small part of the eBook market.

I know, I keep hearing that, but nevertheless it's what I have, what all of my family and friends have, and NONE of them have/use anything other than that -- so we all might be a minority (as far as general statistics go), but in my own life we are certainly the majority.

OUR DAY WILL COME! IPAD SEEN THE PROMISE LAND!

[PeterT]

I thought the promised land came after death, so if you mean iPad will die ..... YEAH