Quote:
Originally Posted by capidamonte
Hey, Your Hitchness!
I didn't see your reply before I PSSSed.
|
I don't know if that was intentional, but
Quote:
Originally Posted by capidamonte
I actually think the best bet is @document with symbolic links. And this all requires the reader to support variables in the first place, of course. Since most readers are based on some sort of linux, symbolic links would give you the simple html address that would work with @document.
|
I appreciate your unconventional ideas, but you're a little off-target here. Symlinks are a *nix OS thing, they don't exist in an ebook rendering environment. That's like saying you should embed a (Windows) Start button in your Microsoft Word document. These things are not quite on the same plane of existence.
Unfortunately, the problem boils down to one of
state. If you want a backlink to change based on where the reader came from, you want your application to have a
state. Full EPUB2 compatibility, AFAIK, means no Javascript, and no JS means no state. No amount of tricky CSS styling will get you anywhere, as that stuff is stateless.
Funny, as I'm about to hit Submit Reply, I actually understood what you meant by symlinks. If you could have each of your hyperlinks hit a symlink that went to the same document, but somehow "defined a different URI for where you were", you could then use the @document directive to use CSS to hide/show the appropriate backlinks. Huh. 10 points for cleverness, but yeah, symlinks are out and @document is an experimental CSS feature :/