Sarai and Jean; This is just a guess, but should she be in paragraph mode before beginning to write her document. Just a thought. I have been having problems getting the paragraph command to work when reading in paragraph mode? Explain that one. Good luck Jean. Terry Powers
-----Original Message----- From: Jean Menzies [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 07, 2005 12:40 PM To: Braillenote List Subject: Re: [Braillenote] reading modes with mPower Hello, Steve, Thanks for those work-arounds. I had come to the same conclusion about having to manually use two carriage returns or two manual spaces in order to get the paragraph reading mode to work right. But I'm still puzzled by the idea that in the Forward Translation options, there is a setting to define paragraph as Next Line. In my thinking, that should then make it so that it would recognize a paragraph with one return. Period. But it doesn't. At least not for documents I create. I hadn't figured out how to search and replace a carriage return, so thanks for that one. My basic thought, though, is that this command needs a bit more fine-tuning. As you said, it would be nice to be able to creat a document once for either embossing or printing without all that fiddling to replace carriage returns, etc. No, I don't want extra blank lines in my embossed documents. I thought all that kind of stuff should be taken care of through the various translation choices. Seems a bit cumbersome to have to do that just to get the paragraph reading and cursor movement commands to work properly. Jean ----- Original Message ----- From: "Steve Speicher" <[EMAIL PROTECTED]> To: "Braillenote List" <[email protected]> Sent: Wednesday, September 07, 2005 7:49 AM Subject: Re: [Braillenote] reading modes with mPower > Good morning, Jean: > > Here are two approaches to the movement-by-paragraph issue. > > 1. As Dean mentioned, a blank line will cause the space-with-2,3 and > space-with-5,6 commands to work as you expect them two. But to get a > blank line, you have to hit the enter key twice. One difficulty with > this approach is that the blank line created in this way is honored > when embossing and so wastes precious space on the embossed page. To > avoid that problem, when you have finished editing the document and > are ready to emboss, you could use the global find and replace to, so > to speak, prepare the document for embossing by converting all > occurrences of the double return to one return followed by two blank > spaces. In the embossed document, the single return followed by the > two blank spaces will give you two-space indents at the beginning of > each paragraph but will not skip a line between paragraphs. If you > want to do some more editing, simply reverse the global find and > replace to convert each occurrence of a return followed by two spaces > to two returns. In the find and replace operation, to produce the > return character, press space with dots 2 and 6. You wouldn't need to > convert back, since the two-space indents created with the first > global replace will now make the move-by-paragraph commands work as > you expect. But you might want to convert back if you want that blank > line between paragraphs for the printing (instead of embossing) of the > document, or if you need to do more editing and just want to save a > keystroke at each paragraph break. > > 2. If you don't mind an extra keystroke at each paragraph break, you > can press enter then add two spaces at the beginning of the new line. > This requires three keystrokes (return and two spaces) instead of two > (two returns); but it makes the move-by-paragraph commands work as you > expect; and it avoids the need for switching back and forth between > two versions of the document, one formatted for reading and one for > embossing. Of course, if you want to print the document rather than > emboss it, you might want the blank line between paragraphs. > > There's probably a third, better way to address the question. I hope > one of our fine listers will post it, as I, too, would like to know > what it is and how to format a document in such a way that it works > equally well for printing or embossing.. > > > > At 07:24 PM 9/5/2005, you wrote: >>Okay. As far as I can figure this out so far, here's what I think is >>happening with moving by paragraph with space dots 2-3 or 5-6. . It >>works fine in any text file. It works fine in any text file converted >>to braille. It works fine in the Demonstration file included in the >>General folder by Humanware. I gather this is a braille document >>created just to play with. Notably, it has one carriage return to >>separate paragraphs. >> >>But I can't move by paragraph in any braille file I create. I've >>experimented with as many combinations of reading mode and thumb key >>combos, but no go. It wants two carriage returns in a braille file in >>order to recognize it as a paragraph. All of the layout options are >>unchanged. >> >>Anyone have any ideas? Could this be a bug or something in 6.2? I >>would assume one shold be able to move by paragraph in a braille doc >>you create. >> >>Jean >> >> >>___ >>To leave the BrailleNote list, send a blank message to >>[EMAIL PROTECTED] >>To view the list archives or change your preferences, visit >>http://list.humanware.com/mailman/listinfo/braillenote >> >> >>__________ NOD32 1.1204 (20050829) Information __________ >> >>This message was checked by NOD32 antivirus system. >>http://www.eset.com > > > > ___ > To leave the BrailleNote list, send a blank message to > [EMAIL PROTECTED] > To view the list archives or change your preferences, visit > http://list.humanware.com/mailman/listinfo/braillenote > > ___ To leave the BrailleNote list, send a blank message to [EMAIL PROTECTED] To view the list archives or change your preferences, visit http://list.humanware.com/mailman/listinfo/braillenote
