View Single Post
Old 05-15-2020, 03:24 PM   #13
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,306
Karma: 13057279
Join Date: Jul 2012
Device: Kobo Forma, Nook
Quote:
Originally Posted by Hitch View Post
Only you and the publisher can decide that. Truly, I'm not copping out; I don't know the extent of your index, how detailed it is, etc.


And in reality, most publishers opt to just remove the index completely. (My personal preference: Just leave the index in, but unlinked.)

As Hitch says, the usefulness of fully linking is 99.9% of the time NOT worth all the extra work needed.*

But but but, there are still some advantages of inserting "RPNs" (especially Accessibility).

Side Note: And again, on the real-life applicability of RPNs... Amazon strips out RPNs from most books. There are only a few rare exceptions allowed (as Hitch discussed a few months ago).

But don't let Amazon's foolish decisions stop you, there's still plenty of EPUB devices/stores out there. And who knows, maybe one day Amazon might get some sense and flip the RPN switch on other types of books, and if your source documents were all prepped ahead of time, you'll be glad.

* Note: Although over the years, I have thought of coding up a little tool to check/link indexes faster+more accurately... but I haven't done any movement on that front.

* * *

Similar argument can be made for proper HTML lang markup.

Currently, there aren't many ereaders that currently make use of it, but in the future, support could be expanded:

(And there still ARE some very nice edge-cases to proper markup: like Calibre's Multi-Language Spellcheck, where it currently is a huge benefit.)

Quote:
Originally Posted by Hitch View Post
I just want to say that realistically, while we've done this (put a target anchor for page numbers at the same location that the original index marker was placed and linked thereto), this is a poor-quality solution. This isn't a criticism of the OP. As I said, we've done it.
Indexing Side Note: And it's extremely rare you'll be working with "fully digital indexes" in the first place.

You would need an actual Word/LaTeX source, linked at the word/paragraph level, plus someone who knew exactly what they were doing with the built-in Index tools.

Hint: Even within professional Indexers, this is an extreme minority.

Most Indexes are created completely externally, and just appended to the end of a document. So you have a "dumb Index" as the only source (even in books that were fully created digitally).

This is kind of like properly using Styles... Properly using Index tools? Absolutely unheard of. :P

Quote:
Originally Posted by 1v4n0 View Post
Sigil's index does link to <p>s, and it is relatively simple to create one when it's just one analytical index (most commonly with personal names). It is however a much longer task to recreate the indexes when there are more than one (for example one for persons, one for places, one for books, etc).
Oh jeeze, Sigil's Index Tool...

It generates completely unhuman-readable mush of "[1], [2], [3], [...], [50]" links for every single word and mangles the HTML throughout the book with disgusting markup.

Similar situation currently happens in a Calibre conversion of a Word document that has a built-in Index.

Side Note: I haven't tested this one in a few years, but even worse, Calibre renumbers all of Word's Index's "page numbers" chronologically in the order they appear. For example:

Actual DOCX Index:

Code:
A: 100, 101
B: 99, 100
C: 50, 101
gets converted into:

Code:
A: [1], [2]
B: [3], [1]
C: [4], [2]
At least Sigil's restarts each word from [1].

Last edited by Tex2002ans; 05-15-2020 at 03:31 PM.
Tex2002ans is offline   Reply With Quote