roger said:
>   That means that anyone who derives a final version
>   (HTML, epub, kf8 etc. file) from it has to find and handle
>   all the markup like intalics and superscripts on their own.
>   It's not coded in the RTT if it's coming out of P2,
>   since formatting is not present in the proofing stages,
>   even inline formatting.
>   That is a serious shortcoming to me.

it's more than "a serious shortcoming".

it's a fatal flaw.

anyone who's done a digitization all the way _knows_
that inline formatting is one of the excruciating parts.

even the "overall" formatting can be a whole lot of work,
but it's generally among the more "fun" parts of the task,
which offsets it a bit.  but we still have to admit it's work.

and some of the finer points (like _proper_paragraphing_)
often take lots of time, relatively, and drive you crazy too.

so to pretend that a text-file that contains no formatting
can be considered as a "master" in any sense of the word
is a denial of reality, one that's silly, if not plain ridiculous.

and jon will learn this very quickly, just like everyone else.

but all you people who know better shouldn't just let him
proceed blithely as if this part of his plan was reasonable...

because it's not.  it's a fatal flaw.

-bowerbird

p.s.  yes, i'm aware that jon said that he'd dialed back
the notion of r.t.t. to sidestep all the "religious" wars.
that doesn't remove the fact that r.t.t. is unworkable.

p.p.s.  no, the irony is not lost on me, not lost at all.
sometimes people on this listserve make _assertions_
that something is true, when that thing is _not_ true,
and has never been true, and likely never _will_ be true.
yet other times when there's something that you _know_
to be true, you just sit on your hands and don't say jack.
it's as if _truth_ means absolutely _nothing_ to you. weird.