john said:
of course I meant _my_ html! Better yet: yours and mine together for others to comment.
i can put up your .html, and link it to your site, so people will understand what it's doing there.
2. Hyphens: I maintain that hyphens not introduced by the author _are_ spurious, but we quibble.
quibbles and bits.
I had not twigged to your use of the hyphen-tilde. Not a bad idea, but it still requires human judgement when the OCR text is being joined up.
yes and no. the software makes an initial decision, based on whether it finds the word in its dictionary. if it does, then it assumes the hyphen is "spurious". if it does not find the joined word, it adds the tilde. there's also some consideration as to how the word appears elsewhere, mid-line, in the book, if it does. this same process could be enacted at "output" time, in which case we could shelve all the tilde business, but then (1) processing would be slowed down a bit, and (2) we wouldn't have a way to force an override. so it depends which powers you want to maximize...
Table of contents is skimpy: This comes down to what are often one-off judgements about presentation.
doesn't mean we can't fight about it. vociferously. :+) i don't think a link that says "chapter 1" is too informative. so if/when a chapter-header does have a descriptive title, i think it should be represented in the table-of-contents... but more important than that, i believe (quite firmly) that each header should _back-link_ to the table-of-contents. and that there should also be a link, at every chapter, for the previous chapter and the next chapter; think about it.
Ever a pleasure interacting with you, BB.
that will amuse many people here. :+)
And I would appreciate criticism from others.
i'd like to see that too, john, but don't hold your breath... -bowerbird