[duxuser] Re: Automatic paragraph styles in 10.5
- From: Dave Durber <dadurber@xxxxxxxxxxxxx>
- To: duxuser@xxxxxxxxxxxxx
- Date: Tue, 01 Mar 2005 10:15:03 -0500
Hello Ann:
Follow these steps to create a style that will produce the type of
paragraphs you want to produce in the braille file.
1. Open the particular file in which you want block paragraphs.
2. Press the key combination<ALT+D> to open the "document Settings"
menu.
3. Press the letter <A> key to open the "Add style..." submenu. DBT
displays the prompt "New style name". Type the following style name
exactly as shown below:
block-para.
The period at the end of the style name, tells DBT that this style is
to be treated as a block style and not a nested style. Nested styles
are styles that can be used inside block styles, which is not the case
with block styles. Nested styles must not have a period at the end of
the style name. This is how DBT knows which are block styles and
nested styles.
4. Press the tab key to move to the "Style can be nested within
another style" check box. By default, this check box is checked. As
we are creating a block style and not a nested style, uncheck the
check box by pressing the <SPACE BAR>.
5. Press the <TAB> key to move to the "Choose style for basis:" list
box. As far as I am aware, there is not a style in any of the default
templates that come with DBT on which we can base the style we are
creating.
6. Press the <TAB> key to move to the OK button and press <ENTER> to
open the two edit fields where we are going to enter the codes for the
style. The cursor is placed in the "Beginning Codes:" edit field.
Type the two codes as follows:
[l][sc1:0]
The [l] code is the (new line code). It will move the text to a new
line if it is not already on a new line.
The [sc1:0] is the (conditional skip line) code. It places a blank
line before the first line of text. One of the benefits of the
(conditional skip line) code, is that when a paragraph ends on the
last line of the braille page and a new paragraph is to start at the
top of the next page, the blank line that would normally appear
between the block paragraphs is dropped.
7. Press the <TAB> key to move to the "End Codes: edit field and
enter the
[l]
code, which is another (new line) code.
8. Press the <TAB> key to move to the OK button and press <ENTER> to
close the dialog box and return you to your document.
If you find that the above style works, you might want to save it with
the use of the "Create template" function which is also found under
"Document settings".
I hope that the above information is of help.
Sincerely:
Dave Durber
On Tue, 1 Mar 2005 07:19:03 -0600, you wrote:
>Well, I'm the biggest dummie in the world because, even after all the
>advice you all have given me about how to create such a style, I still
>can not do it in real life. I wonder why there aren't any styles
>already available in Duxbury to address differing paragraph styles. I
>hope that in some future version, the Word importer will either have a
>choice for the ones most commonly used or a "none" setting so that we
>can expect Duxbury to utilize the paragraph style we set up in our Word
>docs.
>
>
>Ann Foxworth, Braille Consultant
>Div. for Blind Services
>4800 N. Lamar BLVD
>Austin, TX 78756
>PH: 512-377-0471,
>E-mail: ann.foxworth@xxxxxxxxxxxxxxxx
>-----Original Message-----
>From: duxuser-bounce@xxxxxxxxxxxxx [mailto:duxuser-bounce@xxxxxxxxxxxxx]
>On Behalf Of Dave Durber
>Sent: Monday, February 28, 2005 9:22 PM
>To: duxuser@xxxxxxxxxxxxx
>Subject: [duxuser] Re: Automatic paragraph styles in 10.5
>
>Hello Steve, Ann and Listers:
>
>While Steve's suggestion is probably the correct solution for a document
>that will contain block paragraphs from beginning to end, it is
>cumbersome if a document is to contain a mixture of standard formatted
>braille paragraphs and block braille paragraphs.
>
>The reason for this, is that you would have to remember to insert the
>[svprgn:n] code before each paragraph code or style when you wanted to
>change from one paragraph type to the other, as follows:
>
>[svprg0:1]
>
>prior to starting block paragraphs, so that all paragraphs are blocked
>to the left margin and have a blank line before and after each block
>paragraph; and
>
>[svprg3:0]
>
>prior to starting standard formatted paragraphs, where the first line of
>each paragraph is indented to cell 3 and there is no blank line before
>and after each paragraph.
>
>The beauty and advantage of creating styles which contain the correct
>codes built into them, is that if you construct the style correctly to
>produce the desired result, you do not have to remember anything else,
>except apply the correct style at the appropriate places throughout any
>document where you want those types of styles.
>
>This is why when I am preparing documents for transcription to braille,
>I style code documents as much as possible instead of manually coding
>documents.
>
>Some of the advantages of using styles, are as follows: virtually
>eliminates the mistyping the syntax in codes; minimizes the possibility
>of leaving out a code in a string of codes; avoids having to search for
>strings of codes in order to make changes especially if you do not enter
>a string of codes in the same order throughout a document.
>
>On the other hand, if you want to change a code or parameter within a
>code that is contained in a style to alter the output, you only have to
>edit a code or codes contained in a style to affect the output globally
>throughout a document, where that style is used.
>
>In 1995, I transcribed the "JAWS for DOS" manual". I manually coded the
>file from beginning to end. I took nearly four weeks to produce the
>completed work. It contained 6 volumes and had approximately 700 sides
>of braille.
>
>Last year, I transcribed "Verbal View of Word Basics". Except for a few
>codes that needed to be entered manually, I used styles 98% of the time
>to produce the finished book. It contains 7 volumes and has 986 sides
>of braille. It took me 10, 8 hour days to produce the book.
>
>The two examples, do not include the proofreading time.
>
>Sincerely:
>
>Dave Durber
>
>
>
>--
>No virus found in this outgoing message.
>Checked by AVG Anti-Virus.
>Version: 7.0.300 / Virus Database: 266.5.2 - Release Date: 2/28/2005
>
>* * *
>* This message is via list duxuser at freelists.org.
>* To unsubscribe, send a blank message with
>* unsubscribe
>* as the subject to <duxuser-request@xxxxxxxxxxxxx>. You may also
>* subscribe, unsubscribe, and set vacation mode and other subscription
>* options by visiting //www.freelists.org. The list archive
>* is also located there.
>* Duxbury Systems' web site is http://www.duxburysystems.com
>* * *
>* * *
>* This message is via list duxuser at freelists.org.
>* To unsubscribe, send a blank message with
>* unsubscribe
>* as the subject to <duxuser-request@xxxxxxxxxxxxx>. You may also
>* subscribe, unsubscribe, and set vacation mode and other subscription
>* options by visiting //www.freelists.org. The list archive
>* is also located there.
>* Duxbury Systems' web site is http://www.duxburysystems.com
>* * *
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 266.5.2 - Release Date: 2/28/2005
* * *
* This message is via list duxuser at freelists.org.
* To unsubscribe, send a blank message with
* unsubscribe
* as the subject to <duxuser-request@xxxxxxxxxxxxx>. You may also
* subscribe, unsubscribe, and set vacation mode and other subscription
* options by visiting //www.freelists.org. The list archive
* is also located there.
* Duxbury Systems' web site is http://www.duxburysystems.com
* * *
Other related posts:
