Quote:
Originally Posted by Trane
So mentally taking this to the next step, I imagined a reference page for the images... now the question is, should each pic have an internal link to its CC attribution on this separate page?
|
Do you mean a link from Image Caption <-> "CC Acknowledgments"?
Back to my example code, something like this?
I personally wouldn't do it this way, but I don't see why that couldn't work.
Personally, I would just do what was discussed previously. Include a little bit of info in the caption (CC0, CC BY-SA, [...]), and then include the fuller details on the separate "CC Acknowledgments" page.
No need to go cross-linking and re-back-linking or any of that crazy stuff. Imagine you wanted to create a physical copy of this book in the future, now you are just causing yourself extra headaches.
Side Note: And to stress again what JSWolf mentioned... linking a clickable image is probably not the best idea:
Code:
<a href="LinkToSomewhere"><img [...] /></a>
Readers wouldn't be able to pinch/zoom or pan/scan. In many readers you wouldn't even know there was a clickable link there. And there were many versions of ADE that wouldn't allow you to click those types of links (I have no clue if that was fixed in later versions).
Quote:
Originally Posted by Trane
If so, I will have to create dozens of backlinks so the reader can return to where they were reading when they clicked on the picture. (This is a 73k-word book!) Or can I count on e-readers to have a back button and use it? That doesn't seem wise or user-friendly.
|
You may also want to consider a List of Illustrations. It's exactly like a TOC... just points directly to Images instead of Chapters. I think that would be more useful/helpful than a nest of links... and anyone with an older e-ink reader who REALLY wanted to get to a specific image could easily jump to the List of Illustrations directly to any image they need.
If you use meaningful HTML ids + good Numbering Schemes + consistent captions, it shouldn't take long at all to just Regex the entire thing. But this all depends on the specifics of your book + code.
Quote:
Originally Posted by Trane
That is, in fact, exactly what I read, only I came across it on her original site rather than in Techdirt. (Glad you found it b/c I visited dozens of sites that day looking into CC and had no idea how to find it again.)  |
I guess that's what happens when you read about this stuff for years and years: "Hmmmm sounds similar to X, Y, Z." Crazy that I was able to pinpoint that from some random article I read 4 years ago.
