Quote:
Originally Posted by eschwartz
Your Astak is also quite old, isn't it?
|
Wiseguy. (waves at eschartz)
Quote:
I'm afraid I don't know much about what smartphone/tablet ereader apps are out there, or how they compare.
But I am convinced at least one of them has both a back button and a pagenumber indicator. It is inconceivable that you are the only one who wants a standard feature. 
|
You know what? I'd LIKE it if this could exist. It would solve what is a fairly consistent problem for us, which is making clients happy that want internal linking, for this or that, for "many to one" (anchor/target) linking scenarios.
We have one in, right now. GREAT client, been a delight to work with (would that I could clone this guy and his sister), a book I believe in (non-fiction about saving/finding/etc. lost pets), etc. In the course of the book, they have numerous "see XXXX" links. And they are the many to one type. Many "See XXX," with a shared target. Not all, of course, but if there are 10 target resources, let's say there are 50 departure points. The client happens to have a reader that, lo, does not have a "back" button. (n.b.: not all that we have here, do either).
They asked me for this x-refs, and we obliged. In testing them, he realized that no matter how many times he clicked "back" the back link wouldn't go to the 2nd, 3rd, etc., in sequence. I wish I could make it so. I do.
BTW: This, along with font-embedding, seems to be one of those things that I don't explain well. The many-to-one linking problem (for glossaries and the like).
AND, may I add,
many of the desktop software readers don't have BACK buttons,
either.
Just sayin'.
Hitch