Quote:
Originally Posted by paperwhite13
Thank you for the pointers!
No, it is just in this case (main chapter titles, just a couple of them) where the TOC points to the top of the page, otherwise there are dozens of section titles which need the ID's for the TOC to work. I also need the text anchor IDs for the index references, which point to the physical version, so there have to be text anchors spread out for it to work.
|
You don't need two IDs together. In your sample, you can drop the <a> and use the other ID in the index. Have a look and see where you have double IDs and drop one of them. Also, where the ToC is going to the top of the HTML file, if the ID is not needed for the index, you don't need that ID.
Quote:
|
Yes, it's the publisher’s request that on the devices that support publisher styles/font it should appear the same as the physical version, hence the fonts and the styling. It works very well on KBReader, Lithium, latest KOReader on my Kindle PW3, drop caps included on some of them. Whether that's beautiful or ugly is irrelevant for this thread.
|
The thing is, do the fonts used in the book work well on an eInk Reader? Do they have enough weight? If they don't, then they won't work. I've seen plenty of eBooks using the same fonts as the pBook and they do not work as they are too light. Besides, On some Readers, such as a Kinde, these fonts probably won't be seen. On some you are forcing the user to use fonts that are not good. Tell that to whoever is in charge. Show him/her how well that fonts do not work.