View Single Post
Old 08-14-2017, 12:02 AM   #7
Tex2002ans
Wizard
Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.
 
Posts: 2,297
Karma: 12126329
Join Date: Jul 2012
Device: Kobo Forma, Nook
Quote:
Originally Posted by Hitch View Post
Map won't work. You need javascript for that, and 99% of all eReaders don't have that type of publisher-exploitable javascript.
<map> is actually built into HTML itself:

https://www.w3schools.com/tags/tag_map.asp

but yeah... that won't work in most actual ereaders. While <map> is "officially a part of the EPUB spec":
  1. ADE doesn't support it (at least in EPUB2. No idea about their EPUB3 renderer). That throws out the vast majority of dedicated ereaders.
  2. Many devices are not touch screen... so there would be no way to click a certain area.

... and I know this wasn't brought up, but I don't even believe Kindles support <map>. I don't see mention of it anywhere in the Kindle Publishing Guidelines.

Quote:
Originally Posted by taneal1 View Post
My desire is to use an IMG as a Chapter to Table of Contents link rather than text. This would allow "stylized" text within a graphic as the link, without also including otherwise unnecessary text.

This may consider this a "frill", but the graphic would be quite helpful to a child who is learning to read, has limited reading skills, is learning a 2nd language, etc.
Even if you just wrapped an image in a normal link, such as:

Code:
<a href="../Text/TOC.xhtml"><img src="../TableofContents.png" /></a>
there are also quite a few bugs/quirks in readers themselves:
  1. Links around images on some devices will not work at all. It will just act as if it was a normal <img>.
  2. This will interfere with pan/zoom functionality.
  3. There may be absolutely zero indication the image is even clickable. (Unlike a normal hyperlink that is blue+underlined.)

Last edited by Tex2002ans; 08-14-2017 at 12:12 AM.
Tex2002ans is offline   Reply With Quote