MobileRead Forums - View Single Post - [Plugin] ePub3-itizer

Fedwin · 03-19-2015, 08:10 PM

@KevinH

I think I see what you mean by "nav#toc ol" and that makes sense, as plenty of books have other lists in them that may be numbered. I didn't recall any lists in the epubs I converted today, so didn't worry about it; I just included a link to the already existing stylesheet and added the list-style-type: none to the existing stylesheet.

I moved the nav.xhtml file to the second position, just after the cover. Most books usually have it after the title and copyright, but every book is different and it seemed easiest to just put it second.

The books I converted today all had dedicated toc files, although like you said, some were not identifiable by name and I had to open a few html files before I found the toc.

Deleting the toc.xhtml before conversion would have saved me some work fixing the links. In the nav landmarks section and in the toc.ncx , there was always a link to the old toc.xhtml file. A few of the books had links in the chapter titles that linked back to the toc.xhtml. I changed those with a search and replace, but I had to see what to search for first and sometimes they were links to specific lines and not just the file. I think deleting the toc.xhtml file before I convert the book is what I will be doing going forward.

@DiapDealer

I think the spec is saying to ereader manufacturers and ereading software developers: You must display the nav as an unnumbered list UNLESS the epub specifies otherwise and you feel like allowing something other than nothing. It looks silly seeing, "1. Chapter 1: The First Chapter, which comes first," or even worse, "3. Chapter 1: Which We Thought Was First, but Appears to be Third." I can't imagine a hardware or software developer making a product for epub3 that wouldn't let the epub use CSS, but if such an abomination were to be created, it MUST display the nav as an unnumbered list or the IDPF will send around a guy with a sock full of pennies to explain it again. I think.

03-19-2015, 08:10 PM	#53
Fedwin Enthusiast Posts: 28 Karma: 10 Join Date: Dec 2011 Device: PRS-T1	@KevinH I think I see what you mean by "nav#toc ol" and that makes sense, as plenty of books have other lists in them that may be numbered. I didn't recall any lists in the epubs I converted today, so didn't worry about it; I just included a link to the already existing stylesheet and added the list-style-type: none to the existing stylesheet. I moved the nav.xhtml file to the second position, just after the cover. Most books usually have it after the title and copyright, but every book is different and it seemed easiest to just put it second. The books I converted today all had dedicated toc files, although like you said, some were not identifiable by name and I had to open a few html files before I found the toc. Deleting the toc.xhtml before conversion would have saved me some work fixing the links. In the nav landmarks section and in the toc.ncx , there was always a link to the old toc.xhtml file. A few of the books had links in the chapter titles that linked back to the toc.xhtml. I changed those with a search and replace, but I had to see what to search for first and sometimes they were links to specific lines and not just the file. I think deleting the toc.xhtml file before I convert the book is what I will be doing going forward. @DiapDealer I think the spec is saying to ereader manufacturers and ereading software developers: You must display the nav as an unnumbered list UNLESS the epub specifies otherwise and you feel like allowing something other than nothing. It looks silly seeing, "1. Chapter 1: The First Chapter, which comes first," or even worse, "3. Chapter 1: Which We Thought Was First, but Appears to be Third." I can't imagine a hardware or software developer making a product for epub3 that wouldn't let the epub use CSS, but if such an abomination were to be created, it MUST display the nav as an unnumbered list or the IDPF will send around a guy with a sock full of pennies to explain it again. I think.