Nested headings?

[DaleDe]

Originally Posted by crich70

I found two pieces of code to do with links. I'm not sure which is the right one for that.
<a href="#tips">Visit the Useful Tips Section</a>
or
<a name="tips">Useful Tips Section</a>
Or do I have to put one in one place and the other in the actual book files?
I just think it would make for a neater looking ebook file when building an omnibus book.

The first one links to the second one. name= is no longer the preferred syntax. It should be id=

To make a book with in-line links your would place several of the first type in a list on a page. It could be a separate file or just add it to an existing file in your ebook.

The syntax of the first link says the second link is in the same file. If it is really in another file then you might say href="anotherfile.xhtml#tips"

Dale

[crich70]

Thanks. With so much info on the web it's hard to know what is current and what isn't sometimes. I have no idea how old the page I found the bits of code was. I imagine they might have been current at the time, but things can change so fast on the web that I imagine it's hard to be sure of even that.

Originally Posted by DaleDe

The first one links to the second one. name= is no longer the preferred syntax. It should be id=

To make a book with in-line links your would place several of the first type in a list on a page. It could be a separate file or just add it to an existing file in your ebook.

The syntax of the first link says the second link is in the same file. If it is really in another file then you might say href="anotherfile.xhtml#tips"

Dale

[crich70]

So if I understand correctly on the html page I have my cover image on I would have a set of codes that read:
<a href="#book title">book title</a>

and on each of the html pages (in the ebook) I would have:
<a id = "title">title</a>

Is that right?

[Jellby]

Originally Posted by crich70

So if I understand correctly on the html page I have my cover image on I would have a set of codes that read:
<a href="#book title">book title</a>

and on each of the html pages (in the ebook) I would have:
<a id = "title">title</a>

Almost.

I believe you can't have spaces in fragment names, so instead of "#book title" use "#book_title". And you have to use the same name (minus the #) in the id, so use id="book_title".

And you can use the id in any element, not just <a>, so you can have:

<h1 id="book_title">Book Title</h1>

In the future, I'm sure Sigil will have some kind of hyperlink editor that will make all this easier.

[crich70]

Well I have the 2 links on a seperate page now, but when I put it through Calibre the individual chapter links are gone. (I'm using a copy of the Wonderland Books file I created as a model). I'm using the <h1 id="book_title">Book Title</h1> code for the connections. I'm not sure if the h1 rather than an a at the start and end somehow messed things up or if I have to do sometihng like retype all the seperate chapters headings using h2.

[Jellby]

The href="#book_title" works if the target is in the same file inside the .epub. Otherwise, you need to give the path to the other file, like this:

In toc.xhtml (for instance):

<a href="book1.xhtml#book_title">Go to Book Title</a>

(this says: go to file book1.xhtml and there find the element with id="book_title")

and in book1.xhtml:

<h1 id="book_title">Book Title</h1>

It should not matter (for the link to work) whether the element is an <a> or an <h1>, unless something is really buggy in between.

Validating with FlightCrew (in Sigil) should tell you if there's anything wrong.