Dear Jean, What I said in my post applies to all documents.
Terri, Amateur Radio call sign, KF6CA. Army MARS call sign, AAT9PX California On Wed, 7 Sep 2005, Jean Menzies wrote: Hi Terri Yes, that makes perfect sense. But the original discussion started talking about documents created within KeyWord, not those imported or obtained through another source. Does that make a difference? Jean ----- Original Message ----- From: "pann1" <[EMAIL PROTECTED]> To: "Steve Speicher" <[EMAIL PROTECTED]> Cc: "Braillenote List" <[email protected]> Sent: Wednesday, September 07, 2005 3:15 PM Subject: Re: [Braillenote] reading modes with mPower > Dear Steve and List, > > I will try again to explain how to get paragraphs to work right. > > Suppose you have a braille document opened. Each paragraph should > begin > with a hard return followed by two spaces. You want to translate the > document into text and you want the paragraphs in the print document > to > begin with two hard returns. > > Go to the back translation options menu. You will be asked, > "paragraphs > in source document." You would press control enter to indicate the > hard > return and press the space bar twice to indicate the two spaces. I > don't > know what the commands are for a BT keyboard. Now, cycle through the > back > translations list until you come to "paragraph." Press control enter > twice > to indicate you want two hard returns in your print paragraphs. I > don't > know the BT commands. Exit and press y to save the changes. > > Suppose you have a text document you plan to translate into braille. > > Go to the forward translation options list. You will be asked > "paragraph > in source file" If your text document paragraphs begin with two hard > returns, then press control space bar or the equivalent BT command > until > you get to "blank line." Now, cycle through the forward translations > list > until you get to "Paragraph." Press control enter spacebar spacebar > or > the BT equivalent command to indicate you want the paragraphs in the > braille document to be a hard return followed by two spaces. Exit and > save the changes. > > If you want these settings to be the defaults for all your documents, > be > sure to use the forward translation options and back translation > options > in the file manager menu. > > Once you have set up these options, you will be able to open and read > a > braille or text document using the paragraph commands. > > Now, if you want the thumb keys to jump from one paragraph to another, > you > would go to the braille display options and look for thumb keys. > There > are three choices: up and down, sentence or line and paragraph or > section. > Choose paragraph or section. Now your thumb keys will scroll from > paragraph to paragraph. > > I hope this helps. > > Terri, Amateur Radio call sign, KF6CA. Army MARS call sign, AAT9PX > California > > On Wed, 7 Sep 2005, Steve Speicher wrote: > > 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 > > ___ 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
