Quote:
Originally Posted by Jellby
I don't claim to have the perfect solution.
Personally, I don't often find, if ever, links that must be recognized as links. As I think I have said elsewhere, I, as a user, expect some "obvious" things to be links, like references to chapter names or numbers, footnotes, etc. Those, I style with "color: inherit; text-decoration: none". Fortunately the reader I use supports that, and I don't care too much about those that don't, since I don't have clients 
If I was asked to make links stand out, I'd probably choose some colour other than blue (at least change the hue and quality of the default blue) and/or add a border instead of an underline, just to be different.
This applies to the body of a book. I don't care so much about how links may look in the copyright page (when you may have some URL links) or, for instance, the "back" link in footnotes. |
Jellby:
To steal a line from "Steel Magnolias," you know that I love ya better than my luggage, (and I'm always hot for your CSS {smile}), but seriously, as you don't have clients, and you're only making books to meet your own expectations, well, *&^%$#@!
I mean...you don't have to worry that readers won't see the links, or "get" that they are links; you don't have clients that don't understand that night-mode won't work if you have black links...that's an entirely different world.
We have a different environment, plus, for the vast, vast, vast majority of our books, we have Amazon Big Daddy looking over our shoulders. Whole different world. Trust me, if inherit worked everywhere, I'd bloody use it.
Hitch