gee, jim, even when i specifically frame the issue,
you seem incapable of acting in an intelligent way.

the time-stamps _prove_ you spent _less_ than 10 minutes
reading my post, thinking about it, and composing a reply.

perhaps you need to read a little bit more carefully, and
think about the conversation a little bit more thoughtfully.

(right.  like that's ever gonna happen.  nice try, bird.)


>   Sure you are BB, go back and reread what you wrote
>   way back when I introduced this tool to this thread.

i'm quite sure i was supportive of unwrappers back then,
because i have _always_ been supportive of unwrapping...


>   Not at all, its trivial to find where a line of text
>   matches are particular page

"matches are particular page"?  what does that mean?


>   Not at all, its trivial to find where a line of text
>   matches are particular page since any modern
>   text display tool, including DJVU and PDF/A displays
>   include a "find" option to allow you to search on text.

when the text was embedded in the .djvu or .pdf, yes...

but that's not always the case.

besides, you're then advocating that a search be run --
with the person entering a chunk of text from the line
-- for every line you want to check.  that's not optimal.

i've done it that way.  after a while, it gets to be painful.
it's doable.  but it's a far cry from being the _best_ way.
(especially since you're juggling different applications.)

it's far better to set up some kind of search criteria --
"show misspelled words", or "show italicized words"
-- and have the tool automatically summon the scan
for the appropriate page at the next hit on the search.
(just the fact that you've integrated your text-handler
and your scan-handler into _one_ app is a huge win.)

the way you do it might "work", but it's not _efficient_,
in the sense that it would scale into a process that can
handle hundreds of books, let alone tens of thousands,
in a way that the human cost justifies the digital benefit.
(and you know we have millions of books online, right?)

oh, and by the way, maybe just maybe if jim would have
spent a minute to think about it, he would have realized
that the reason a text-search in .djvu or .pdf _can_ lead
you to the page-scan that contains that text is _precisely_
because those formats _retain_ that page-number info...
if they tossed it out, the same way that jim tosses it out,
then they would be in the same situation that he is in...

then again, maybe just maybe jim could've spent _years_
thinking about that issue, and never had that realization.


>   Again, BB, the problem is that you live
>   in a BB-centric world where you believe
>   that the BB-approach is the "only way to fly."

well, that certainly added to the value of this dialog, jim.

(oh, and jim?, it's a good thing that .djvu and .pdf _also_
seem to live in my bb-centric world where we keep track
of the relationship between every line of text and its scan,
or you wouldn't have had anything idiotic to say up above.)


>   Well, again, PG could start by fixing their
>   on-going paragraph formatting problems.
>   That ain't exactly a high-tech problem!

right after -- and i mean _right_after_ -- you talked
about me "living in my own world", you went off and
climbed up on your good ol' paragraph hobby-horse.

i guess anything that allows you to make a connection,
no matter how tenuous, to go off and ride that thing is
all that you need, jim.  but hey, at least we're done here.

-bowerbird