[bksvol-discuss] Re: More Questions on Proofing
- From: "Shelley Rhodes" <juddysbuddy@xxxxxxxxxxxx>
- To: "bksvol-discuss@xxxxxxxxxxxxx" <bksvol-discuss@xxxxxxxxxxxxx>
- Date: Tue, 27 May 2008 22:13:21 -0400 (EDT)
If the pictures, diagrams,tables, or charts do not lend anything to the
book, nuke them! Don't describe them unless you need to!
Is my motto, since the text describes what it is going to do, then I
wouldn't bother describing the screen shots.
Shelley L. Rhodes M.A., VRT, CTVI
and Guinevere, Golden lady Guide
guidinggolden@xxxxxxxxx
Guide Dogs For the Blind Inc.
Graduate Alumni Association Board
www.guidedogs.com
"Courage is not being without fear,
but courage is to go forward in spite of
fear."
----- Original Message -----
From: "Chris Hofstader" <cdh@xxxxxxxxxxxxx>
To: <bksvol-discuss@xxxxxxxxxxxxx>
Cc: "'Jamal Mazrui'" <empower@xxxxxxxxx>
Sent: Tuesday, May 27, 2008 7:31 AM
Subject: [bksvol-discuss] More Questions on Proofing
Hi,
Sorry for the pile of emails but my lovely wife Susan and I are the new kids
on the scanning and proofing block and we run into different curiosities as
we proceed. This question applies to our Drupal book. For those who don't
work on web sites, Drupal is a program that makes building really
interesting web sites relatively simple.
The book has a lot of screen shots (mentioned in my last message) in which
OmniPage 15 recognizes quite a bit of text but never all of it and it often
thinks that a border is a letter "I" or "l" or just some schmootz that it
ignores.
Susan, my lovely wife, was planning on making up descriptions for these
screen shots in a future phase of the reviewing process. She estimated that
this would take a lot of time as there are a lot of these shots. She added
that virtually all of these screen shots do nothing more than show how
Drupal will render a page visually when using features described in the text
that can be read nicely.
Susan has meticulously gone through most if not all of the code samples and
fixed the odd exclamation point that was recognized as an "l" and a few
other single character mistakes that can make code examples boggle one's
mind as parsers rarely have enough intelligence to figure out, "He didn't
mean 'l' but rather, he wanted an '!' in that spot" which will lead to hair
pulling to try to figure out why copy and paste from the document didn't
work.
How valuable will it be to spend a ton of time trying to come up with text
augmentations and annotations to include the screen shots? Keep in mind
that the same time would otherwise be spent proofing other books which may
be a bit less challenging as regards graphical content.
Happy Hacking,
cdh
To unsubscribe from this list send a blank Email to
bksvol-discuss-request@xxxxxxxxxxxxx
put the word 'unsubscribe' by itself in the subject line. To get a list of
available commands, put the word 'help' by itself in the subject line.
--
No virus found in this incoming message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 269.24.1/1468 - Release Date: 5/26/2008
3:23 PM
Shelley L. Rhodes
To unsubscribe from this list send a blank Email to
bksvol-discuss-request@xxxxxxxxxxxxx
put the word 'unsubscribe' by itself in the subject line. To get a list of
available commands, put the word 'help' by itself in the subject line.
Other related posts:
