
by the way, i just thought i would reiterate an old screenshot... perhaps some of the people planting bugs in rfrank's ears will consider pointing him in the directions suggested here:
that's a big screenshot, because i've got a big screen, but the idea is that the proofer does the word-by-word scan _not_ against a web-page's textfield version of the page, but rather against an .html-realized version of the page... (if proofers wanted, you could even use the d.p. font on it.) the main benefit is that you free 'em from having to look at the markup, because that's an unnecessary distraction. they see actual rendered italics, not the markup for italics. it's also possible this way to red-flag any possible scannos, as well as capitalization and punctuation improbabilities... you can also colorize quotations, which helps locate any missing or incorrect quotemarks. like i said, i have a big screen, so i can put up 3 pages -- the textfield, the original scan, and the .html version, but for a smaller screen, you'd put up the scan and the .html. then, only if there are changes to be made will the proofer summon the textfield for editing. i also show lots of buttons on the screen. some are there to add words to the book's custom dictionary, so that you don't have to have them flagged the next time they appear. the others are just marked with numbers, to indicate things that they could be used for, such as italicizing selected text. again, proofing the .html version is easier than the textfield. -bowerbird

On 3/3/2010 4:16 PM, Bowerbird@aol.com wrote: [snip]
the idea is that the proofer does the word-by-word scan _not_ against a web-page's textfield version of the page, but rather against an .html-realized version of the page... ... the main benefit is that you free 'em from having to look at the markup, because that's an unnecessary distraction. they see actual rendered italics, not the markup for italics.
FWIW, I like this idea very much. I think it meshes quite nicely with Mr. Frank's notion that markup should never be separated from its associated text.
it's also possible this way to red-flag any possible scannos, as well as capitalization and punctuation improbabilities...
you can also colorize quotations, which helps locate any missing or incorrect quotemarks.
This would have to be done subtly, so as not to influence users to make changes where they are inappropriate, but I think the idea has merit. [snip]
then, only if there are changes to be made will the proofer summon the textfield for editing.
The Kupu editor which is part of the Plone and Apache Lenya projects could be a very nice choice for this editor (good software engineers never want to reinvent wheels). In fact, I think it may be possible to use Lenya to build a prototype of this very sort of application. I'll do a little research and get back to you.
participants (2)
-
Bowerbird@aol.com
-
Lee Passey