Quote:
Originally Posted by signum
I, too, am quite comfortable looking at html, but I think you've missed the point I was trying to make. During the final read-through, I'm looking at the visual effect of the entire page, among other things. I'm reading the text word-for-word looking for things, such as mis-placed hyphens, that don't just pop out at you in code view. In my opinion, the markup codes obscure the final result at this point. Hyphens are very easy to remove with just a tap of the backspace or delete key, without having to switch to the code view. Improperly aligned headings pop out at just a glance. It's all visual at this point after I've done all the spell checking, removed all validation errors and made sure all curly quotes match.
I try to think like the end user, who probably will never see the html markup.
|
Well, yeah, but they're not going to look at the book like you do, anyway, whether it's BV, Preview, or ADE, or anything else. They'll see it however they see it, on whatever devices they have, fonts they choose, etc., no? Myself, I test the books on ADE, or (better yet) Sony Reader. That gives me a much better visual check, IMHO.
Quote:
|
FWIW, my first browsers were ViolaWWW, Cello and NCSA Mosaic on a 286 running Windows 3.1. Perhaps you remember them?
|
Nah--I used Lynx.
Still do, as a matter of fact. It was my first "browser," per se. Before Lynx, I used ye olden Archie, along with Jughead and Veronica for Gopher. (Using, way back, OS/2, which I thought was really great, myself. Died for lack o'love (drivers)). Added 3.1 in...what, spring of '88? Or thereabouts? We still have a box here running OS/2. Hell, for that matter, we have one here running Win98 (used to drive a Mill!).
Hitch