
james- good job on the feedback. my replies are appended. you now have some new .html versions to preview... here's the full version:
and a version which scrunches ordinary paragraphs:
the latter version makes it much easier for you to check the paragraphs with some kind of "special" formatting... the formatting is now close enough for you to finish off. the next step will be to do a global correction of names. in that regard, you might wanna do a quick look at this:
these are the bulk of the words that "failed" spellcheck. as is usually the case, the ones with an initial cap are almost exclusively names, and most of 'em are correct. i'll give you another version of this list later that tells us with far greater certainly which of them are likely right... the words that are listed in lowercase, at the bottom, are more likely to be scanning errors, as you can see, while there's also a mix of british spelling and words specific to this particular book, which is also typical... once we add the appropriate words to the dictionary, you'll do a focused correction of the remaining terms, after which there'll be very few words that get flagged while you're doing your page-by-page read-through, which will enable you to focus on punctuation glitches. i've got some other stuff brewing today, but i'll try to get to those names as soon as i can. in the meantime, if you're antsy to do some work, do more family trees... *** al said:
Can't help you with Bowerbird. To borrow a phrase, "you've made your bed, now..." <g>
i guess i must have missed the part where al offered to help you on this book, james. maybe he said that he'd re-do the o.c.r. for you, using abby finereader? yeah, i must have missed that... :+) -bowerbird
Page 1 color-coded text should be a single blockquote.
who is being quoted? no, those are simple paragraphs. you can decide if you want them to have just an indent -- which means only the first line will be indented -- or whether you want the left-margin to be adjusted, in cases where reflow causes the first line to be split. but it would be "tag abuse" to call these "a blockquote".
Page 11 color-coded text could be a blockquote.
again, who is being quoted? this probably should be a list. but i'd be inclined to mark it up as a plain old paragraph... ok, no, i take it back, let's just call it a list. that's what it is.
Page 13 blockquote for the first colored section
nope again on the blockquote. once again, this is a list...
pre for the family tree below it.
all the family trees will be tagged as "pre", no question...
Page 15 should be blockquotes.
just indented paragraphs, as far as i can see...
Page 21 pre tag, I guess. I'd probably make an HTML table for this myself, but I don't see how you could do that automatically.
i did this table for you. if you look at it in a monospaced font, you'll see it all lines up. however, it's not necessary to do that. a space in column 1 and the vertical-bar in column 2 signify a table in z.m.l. vertical-bars also demarcate your columns. these vertical-bars need to have a space on either side of 'em. (except the rightmost one does not need a space to its right.) right now, i'm just marking all the tables with a "pre" tag, but in a future iteration, the software will make real .html tables.
Page 25-6 block quotes. This is really a multi-level outline so if I was doing it by hand I'd use nested block quotes.
i'll have to dig out my sample code for multi-level outlines. but for now, i'll just leave all these as ordinary paragraphs.
Page 30 top one block quoted section.
it's a list.
Page 30 bottom - 31 I'd probably reformat (using words instead of ") so it worked as a blockquote.
i did it as a table.
I'd rework the formulas so they could be read in a proportional font and still make sense. Example: 1 Manvantara = 12,000 x 1,000 / 14 = 857,142 6/7 Deva years.
great idea. i'll let you do that.
Page 46 is a footnote.
is that the only footnote in the book? if so, i'd just leave it as is.
You seem to be double-spacing my family tree tables.
i probably forgot to take out the "br" tags in a "pre" paragraph.
We had also talked about doing both illustrations from the book *and* ASCII art to represent family tree tables. Does light markup work in that scenario?
make the illustration, and then pull it in. see the example on page 11 to figure out how to have an illustration shown.
Page 82 will eventually be an HTML table.
i did it as a table. i chopped it in half for you.