The "old key" is the alt key. I suspect "old key" is a dictation oopsie.
K On 8/5/14, Robert Hebert via Jfw <[email protected]> wrote: > On Monday, August 5th at 4:44 P.M. Ed Marquette wrote: > All of this is helpful. > I think there was one error, however. > To access the quick access toolbar, one uses the old key plus the numbers > on > the number row. > So, Ed, what exactly is the "old Key?" > -----Original Message----- > From: Jfw [mailto:[email protected]] On Behalf Of Ed Marquette > via Jfw > Sent: August-04-14 4:42 PM > To: Kimber Gardner; The Jaws for Windows support list. > Cc: The Jaws for Windows support list. > Subject: Re: JAWS and MS Word 2010 comments > > All of this is helpful. > I think there was one error, however. > To access the quick access toolbar, one uses the old key plus the numbers > on > the number row. > The big problem is exiting comments. > > > Sent from my iPhone > >> On Aug 4, 2014, at 10:42 AM, Kimber Gardner via Jfw > <[email protected]> wrote: >> >> Hi Adrian, >> >> I feel your pain as I regularly do the comment swap with my own >> editors and it is a pain in the butt. >> >> As Doug said, editing the comment is the only way I know to move >> through the text of a comment by words or characters. I wish there >> were a more efficient way but alas there isn't. >> >> As for accessing and reading the comments themselves, there are times >> when I prefer the ms word functions for previous and next to the jaws >> method. The most efficient way to utilize the ms word previous and >> next comment functions is to place them on the quick access toolbar >> which you can then access via the control key and one of the keys in >> the numbers row on the keyboard. >> >> Another helpful tip is to set up jaws to use one of the proofing sound >> schemes. I can't recall exactly which one I use, but will figure it >> out and get back to you if you'd like. >> >> In my case, my line editors use color coding to indicate various types >> of editing, like green for repetitions and pink for unnecessary words. >> If you have a need to know which words have been colored, the best way >> to do this is with the ms word find highlight function. I can provide >> instructions for this too if need be. >> >> That's all I can think of right now. Let me know if you need more >> details and I will do my best to help. >> >> Kimber >> >>> On 8/3/14, Adrian Spratt via Jfw <[email protected]> wrote: >>> Hi. An editor wants to use Word 2010's comments to send me her >>> thoughts on a 300-page document. I've never used this feature before. >>> She has sent me a short sample to see if JAWS can read the comments. >>> >>> After reading a number of posts I saved on the subject from this list >>> and the relevant section in CathyAnne Murtha's textbook, I cannot >>> solve the following problems. >>> >>> I know to bring up comments in context by pressing > control+shift+apostrophe. >>> With Windows key+semicolon, I can also create a text file consisting >>> of all the comments. Here are the problems I've identified so far: >>> >>> 1. When reading a comment in context after pressing >>> control+shift+apostrophe, I'd like to navigate it with the arrow keys. >>> However, nothing happens. I can repeat the entire text to my heart's >>> content, but not isolate words and phrases. >>> >>> 2. I can isolate words and phrases when I bring up all the comments >>> in the Win key+semicolon text file. However, this is not ideal for two > reasons. >>> First, it will require me to do a lot of cross-referencing between >>> the document's primary text and the comments page I've created. >>> Second, after checking the JAWS text against a sighted person's >>> reading of the text in the printed comments, I find there's additional > text in the JAWS version. >>> Additional text might be a smaller problem than less text, but it is >>> distracting and makes me worry that the JAWS version might prove >>> unreliable in other ways. >>> >>> Here's a sample comment. Everything after the peculiar word "extrahat" >>> appears in the JAWS version but not the print original: >>> >>> Here's where a comment would go. My Word program identifies what >>> words in the text this comment is about by coloring them and giving them > a number. >>> Extrahat the comments appear in two different places--one, in a list >>> on the left hand sidey coloring them, and giving them a nu >>> >>> 3. All in all, for a JAWS user, this seems a terribly cumbersome >>> process, especially for a 300-page document where there will be >>> comments on nearly every page, as well as strike-through and other >>> attributes. Am I just showing the anxiety of one new to a task? Is >>> there a method that will work better for me and is equally convenient >>> for > the editor? >>> >>> I hope I've made myself clear. Thanks especially to Ed Marquette and >>> Jean Menzies for their posts on this topic. >>> -------------- next part -------------- An HTML attachment was >>> scrubbed... >>> URL: >>> <http://lists.the-jdh.com/pipermail/jfw_lists.the-jdh.com/attachments >>> /20140803/42ed91ce/attachment.html> >>> _______________________________________________ >>> Jfw mailing list >>> [email protected] >>> http://lists.the-jdh.com/mailman/listinfo/jfw_lists.the-jdh.com >>> >> >> >> -- >> Kimberly >> >> _______________________________________________ >> Jfw mailing list >> [email protected] >> http://lists.the-jdh.com/mailman/listinfo/jfw_lists.the-jdh.com > > _______________________________________________ > Jfw mailing list > [email protected] > http://lists.the-jdh.com/mailman/listinfo/jfw_lists.the-jdh.com > > > _______________________________________________ > Jfw mailing list > [email protected] > http://lists.the-jdh.com/mailman/listinfo/jfw_lists.the-jdh.com > -- Kimberly _______________________________________________ Jfw mailing list [email protected] http://lists.the-jdh.com/mailman/listinfo/jfw_lists.the-jdh.com
