Quote:
Originally Posted by KevinH
That approach would miss or break ids used by the epub2 toc.ncx which use <content src="blah#fragment">, and of course break the opf guide urls if they used fragments, and any ncx pagelists or adobe pagmap.xml use of fragments.
|
For me, tox.ncx and the OPF file get the anchors removed from the URLs
if there is only one anchor that points to a file. If the content is split to a new file each chapter, then I have yet to find a book that needs the ID...pointing to the top of the page is good enough.
Also, I have seen a couple of books where the actual link in the ToC was to the beginning of the text of the chapter, not the chapter name/number. And the chapter name/number used a graphic that was quite large, or there was a large top margin. On a small screen reader, this caused the ToC to jump to the text, but you were never quite sure that you clicked the right chapter in the ToC until turned to the previous page to see the chapter name/number.
Quote:
|
Not to mention epub3 external cfi urls that use fragments, external bookmarks that use fragments, javascript uses to dentify nodes in the dom, etc.
|
For my personal library, I don't care about external links between books, because none of my readers support them. Even if they did, I'd still probably remove them, as I don't have a use for them.
My big problem with IDs is that the obvious ones (chapter, etc.) aren't really a problem. But, I run into books where every element (p, span, h1, div, etc.) has its own unique ID, and none are referenced within the book. I doubt they are referenced outside the book, either. So, they all get removed.