[bksvol-discuss] Re: Creating a Process for Creating Guidelines
- From: "Robert Peters" <rpet@xxxxxxx>
- To: <bksvol-discuss@xxxxxxxxxxxxx>
- Date: Fri, 12 Jun 2009 19:55:19 -0500
Ma'am,
I did what you said the second time--not the first time. The "match
case" is not checked by default--as it is in WordPerfect. We'll see how this
works.
RKP
Attention: The information contained in this message and/or attachments is
intended only for the person or entity to which it is addressed and may contain
confidential and/or nonpublic material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon, this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
delete the material from any system and destroy any copies.
>>> "Mayrie ReNae" <mayrierenae@xxxxxxxxx> 6/12/2009 7:43 PM >>>
Hi Robert,
Did you make sure to check the box to have word respect case
sensitivity? If you type a lower case letter j and check case sensitivity,
the lower case letters will be the only letters checked.
I can't imagine why an upper case J would be replaced by a lower case j.
Unless you typed the letters shifted (capitalized) in the find box and
unshifted (not capitalized) in the replace box. Try making sure that case
sensitivity is checked and that you use the case (upper or lower,
capitalized letters or not) where you intend each to be.
Good luck.
Mayrie
-----Original Message-----
From: bksvol-discuss-bounce@xxxxxxxxxxxxx
[mailto:bksvol-discuss-bounce@xxxxxxxxxxxxx] On Behalf Of Robert Peters
Sent: Friday, June 12, 2009 11:35 AM
To: bksvol-discuss@xxxxxxxxxxxxx
Subject: [bksvol-discuss] Re: Creating a Process for Creating Guidelines
Thanks, and I'll try it. I have just done a replace using Word, and I was
even able to get rid of the "registered trademark" symbol; I also got rid of
the linebreaks; the only problem I have is that it gets rid of capital
letters where they are the first word in a line. If they're paragraphs, it
looks okay. But, if the sentence is: " He asked (linebreak) Johnny what
time it was." "Johnny" comes out "johnny." I'm not sure that a very big
problem. Though this is a rationalization, British Braille doesn't even use
the capital sign--or didnt forty or fifty years ago.
RKP
Attention: The information contained in this message and/or attachments is
intended only for the person or entity to which it is addressed and may
contain confidential and/or nonpublic material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
delete the material from any system and destroy any copies.
>>> "Mayrie ReNae" <mayrierenae@xxxxxxxxx> 6/11/2009 1:45 PM >>>
Hi Lori, and Robert,
I'm really, really, sorry. My command was WRONG! Robert, it
doesn't work because I was wrong and didn't check it. Really, really sorry.
I hate it when I misinform.
Thank you Lori so much for fixing my booboo.
Just went to test. With JAWS, this does not work, Lori and Robert.
You have to enable some junk in JAWS verbosity. My live-in geek discovered
that. I don't know how to do it myself. Have fun playing in verbosity,
Robert.
Mayrie
-----Original Message-----
From: bksvol-discuss-bounce@xxxxxxxxxxxxx
[mailto:bksvol-discuss-bounce@xxxxxxxxxxxxx] On Behalf Of Lori Castner
Sent: Thursday, June 11, 2009 11:03 AM
To: bksvol-discuss@xxxxxxxxxxxxx
Subject: [bksvol-discuss] Re: Creating a Process for Creating Guidelines
Robert,
Someone mentioned yesterday that the JAWS command to releal the codes is
alt+control+8.
However, I use Windoweyes, and a word command for "show all" is
shift+control+8. Give that a try in Word.
Lori
----- Original Message -----
From: "Robert Peters" <rpet@xxxxxxx>
To: <bksvol-discuss@xxxxxxxxxxxxx>
Sent: Thursday, June 11, 2009 8:32 AM
Subject: [bksvol-discuss] Re: Creating a Process for Creating Guidelines
> Nancy,
> I have figured out how to take the linebreak characters out using Word
> Perfect. You don't have the issue with capital letters in Word
> Perfect, which you appear to have in Word. My problem--and it is
> probably a function of my sixty-eight years--is that I need to keep a
> running list of
> the last letter preceding whose linebreak I have just deleted.
> Someone yesterday posted how to get the reveal codes in Word. I tried
> what I thought it was (alt/ctrl/8) and it did not work. Did I mess up?
> RKP
>
>
>
> Attention: The information contained in this message and/or
> attachments is intended only for the person or entity to which it is
> addressed and may
> contain confidential and/or nonpublic material. Any review,
> retransmission, dissemination or other use of, or taking of any action
> in reliance upon, this information by persons or entities other than
> the intended recipient is prohibited. If you received this in error,
> please contact the sender and delete the material from any system and
> destroy any
> copies.
>
>
>>>> "Nancy Martin" <nancyam@xxxxxxxxxxx> 6/10/2009 7:26 PM >>>
> I agree.
> ----- Original Message -----
> From: EVAN REESE
> To: bksvol-discuss@xxxxxxxxxxxxx
> Sent: Wednesday, June 10, 2009 12:02 PM
> Subject: [bksvol-discuss] Re: Creating a Process for Creating
> Guidelines
>
>
> I don't see why you would not just skip over the info for programs or
> equipment that you did not have and just read the stuff that applies
> to what you do have.
>
> Evan
>
> ----- Original Message -----
> From: Rogerbailey81@xxxxxxx
> To: bksvol-discuss@xxxxxxxxxxxxx
> Sent: Wednesday, June 10, 2009 10:08 AM
> Subject: [bksvol-discuss] Re: Creating a Process for Creating
> Guidelines
>
>
> I can see a definite value to having these suggestions incorporated
> into the manual. However, thinking back to almost a year ago when I
> first became a volunteer, if I had read a manual that long an
> complicated I think I might have been intimidated into backing out. If
> I saw a lot of instructions dealing with programs and equipment I did
> not have I might have decided that I was unable to volunteer at all.
>
> "I find
> capitalism repugnant. It is filthy, it is gross, it is alienating...
> because it causes war, hypocrisy and competition." Fidel Castro
>
> The Militant: http://www.themilitant.com/txtindex.shtml Pathfinder
> Press: http://www.pathfinderpress.com
> Granma International: http://granma.cu/ingles/index.html
> _
>
> table with 2 columns and 6 rows
> Subj:
> [bksvol-discuss] Re: Creating a Process for Creating Guidelines
> Date:
> 6/10/2009 9:42:40 AM Eastern Daylight Time
> From:
> rpet@xxxxxxx
> Reply-to:
> bksvol-discuss@xxxxxxxxxxxxx
> To:
> bksvol-discuss@xxxxxxxxxxxxx
> Sent from the Internet
> (Details)
> table end
>
> As an Openbook user, and someone who has had four books rejected, I
> concur.
> Robert
>
> Attention: The information contained in this message and/or
> attachments is intended only for the person or entity to which it is
> addressed and may contain
> confidential and/or nonpublic material. Any review,
> retransmission, dissemination or other use of, or taking of any action
> in reliance upon, this information
> by persons or entities other than the intended recipient is prohibited.
> If you received this in error, please contact the sender and delete
> the material
> from any system and destroy any copies.
>
> >>> "Nancy Martin" <nancyam@xxxxxxxxxxx> 6/9/2009 10:03 PM >>>
> Hi Pavi and list,
> One presumably change which should be made in the manual is that
> books are initially checked for fourteen days and not 30 as the manual
states.
>
> I personally would like to see program-specific sections in the manual.
> For example, a section on using MS Word to proof books. The section
> might
> include
> a checklist type approach with instructions for accomplishing those
> tasks. For example, 1. check and fix fonts with appropriate instructions.
> 2. taking
> out paragraph breaks with Word instructions. This would help
> proofers make sure they remembered to do all these things before
submitting a book.
> Another
> set of instructions would be written for OpenBook, Kurzweil 1000, etc.
>
> I hope I'm making some sense.
> Just my two cents worth,
> Nancy Martin
> Oklahoma
> ----- Original Message -----
> From: Pavi Mehta
> To: bksvol-discuss@xxxxxxxxxxxxx
> Sent: Tuesday, June 09, 2009 4:06 PM
> Subject: [bksvol-discuss] Re: Creating a Process for Creating
> Guidelines
>
> That's great to hear Christina! It's definitely possible to have
> you be on the team. Judy S. has also volunteered to be a part of it.
> As more feedback
> comes in we will keep everyone posted.
>
>
> All good things,
>
> Pavi
>
>
> From: bksvol-discuss-bounce@xxxxxxxxxxxxx
> [mailto:bksvol-discuss-bounce@xxxxxxxxxxxxx] On Behalf Of Christina
> Sent: Tuesday, June 09, 2009 2:03 PM
> To: bksvol-discuss@xxxxxxxxxxxxx
> Subject: [bksvol-discuss] Re: Creating a Process for Creating
> Guidelines
>
>
> Hi, Pavi.
>
> This guideline shapers group is a wonderful idea.
>
> I'd like to be included on this team if that's possible.
>
> Christina
>
>
> ----- Original Message -----
>
> From: Pavi Mehta
>
> To: bksvol-discuss@xxxxxxxxxxxxx
>
> Cc: carrie.k@xxxxxxxxxxxxx
>
> Sent: Tuesday, June 09, 2009 4:26 PM
>
> Subject: [bksvol-discuss] Creating a Process for Creating
> Guidelines
>
>
> Hi All,
>
>
> As you know the recent guidelines that went out on Page
> Numbering have generated some understandable concern and confusion
> among the volunteers. Some
> of you have written in to staff with detailed emails articulating
> those
> areas of concern and where the guidelines appear more inconvenient
> than helpful.
> Others have expressed their opinions on the list. Carrie and I have
> had
> several discussions recently on how best to address these concerns and
> modify the
> guidelines so that they serve as a tool and not a hindrance. As
> hands-on volunteers all of your input is valuable and we want the
> guidelines to reflect
> the best practices and collective wisdom of the volunteer community.
>
>
> Regarding page numbers Carrie will send out a note shortly to
> clarify some of the areas of confusion and concern and explain how the
> guidelines for
> this will be implemented. Bottom line is that we do understand the
> wide
> variety of challenges volunteers face with including page numbers in
> books, and
> we're glad to have had your feedback. We intend hereon for this
> guideline to be implemented with a large degree of flexibility - and
> will be rewriting
> the guidelines to clearly reflect the difference between page
> number requirements for educational books and other submissions.
>
>
> Moving forward though, for us one of the overarching questions
> that
> the Page Number issue brings up is:
>
>
> What is the most efficient and effective way for Bookshare to
> do the following:
>
>
> 1. Identify volunteer areas that need guidelines
>
> 2. Draft guidelines and have them reviewed by a small pool of
> volunteers(in a sort of beta phase)
>
> 3. Finalize and share these guidelines among the greater
> volunteer community
>
>
> Ideally, Carrie and I feel that volunteers should have a
> leading and more transparent role to play in steps 1 and 2 above.
>
> Here is a suggested approach, that it would be great to get
> your input on:
>
>
> 1. Form a self-selected team of "Bookshare Guideline Shapers"
> (we can think of a better name down the line- smile). The Guideline
> Shapers are
> Bookshare volunteers who step forward to help identify, draft and
> sound
> out missing guidelines. Even if something is brought to staff
> attention regarding
> a missing guideline, we would turn it over initially to this group
> with
> our suggestions if any.
>
>
> 2. The Guideline Shapers would decide on areas that need
> guidelines, work on an initial draft of these guidelines and then send
> them over to
> Carrie/me for review from the Bookshare staff perspective. The
> Guideline Shapers would go over any edits from us and come up with a
> revised guideline.
> They would then solicit feedback on the guideline from the
> volunteer list before making any final tweaks to it.
>
>
> 3. Once the guideline has been finalized, I will incorporate
> it in the Volunteer Manual, and ensure that it is announced on the
> volunteer blog
> as well as on the volunteer discussion list. (We will create a
> separate
> section of the manual for Updates to the Manual so that it is easy for
> people to
> keep up with the changes).
>
>
>
> Participation from the volunteer community while shaping
> policy, we
> feel is key and we think this approach could be a really invigorating
> way of facilitating
> the creation of useful guidelines from the inside-out. Of course we
> would be more than glad to help with the logistics of setting up a
> group alias and
> other etcs for Guideline Shapers, and to provide assistance
> wherever we
> can. We would love your feedback on this approach as well as to know
> if any of
> you are interested in being part of such a team.
>
>
> Warm regards,
>
>
> Pavi & Carrie
>
>
> Pavi Mehta
>
> Volunteer Coordinator, Bookshare
>
>
> Benetech
>
> 480 S. California Ave., Suite 201
>
> Palo Alto, CA 94306-1609 USA
>
> Phone: +1 650 644-3459
>
>
> pavim@xxxxxxxxxxxx
>
>
> www.benetech.org
>
>
> The Benetech Initiative - Technology Serving Humanity
>
> A Nonprofit Organization
>
>
> 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.
>
>
>
> **************
> Download the AOL Classifieds Toolbar for local deals at your
> fingertips.
>
(http://toolbar.aol.com/aolclassifieds/download.html?ncid=emlcntusdown000000
04)
> 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.
>
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.
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.
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.
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.
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:
