[duxuser] Re: Still Struggling with TOC

  • From: "Susan Stageberg" <stageberg.susan@xxxxxxxxxxxxxxxxx>
  • To: <duxuser@xxxxxxxxxxxxx>
  • Date: Wed, 7 Apr 2004 08:12:35 -0500

Oh good grief, Dave. I knew it was something silly like that. Thank you
very much indeed. Beware all: paragraph styles have a period in the
syntax. I shall now go back in my corner.



Susie Stageberg
Project ASSIST with Windows
Iowa Department for the Blind
(515) 281-1351 

-----Original Message-----
From: duxuser-bounce@xxxxxxxxxxxxx [mailto:duxuser-bounce@xxxxxxxxxxxxx]
On Behalf Of Dave Durber
Sent: Tuesday, April 06, 2004 7:31 PM
To: duxuser@xxxxxxxxxxxxx
Subject: [duxuser] Re: Still Struggling with TOC


Hello Susi:

Please ignore my previous incomplete message.

Thank you for sending me the file.

When I opened the file, it was immediately apparent as to why DBT's
Table of Contents Generator was not able to produce the result that you
wanted.

You typed the beginning and ending style commands as follows:

[es~h1]
[ee~h1]

I looked at the list of styles but, there wasn't a style in the list
that corresponded with that syntax.  However, there was the default
heading level 1 style with the syntax for the beginning and ending style
commands as follows:

[es~h1.]
[ee~h1.]

As you will see, in the second example, there is a period before the
right square bracket in the beginning and ending style commands.

Perform a Search and replace function.  Search for: [es~h1] which is the
beginning style code that already exists in the document and replace it
with: [es~h1.]

Perform a Search and replace function.  Search for: [ee~h1] which is the
ending style code that already exists in the document and replace it
with: [ee~h1.]

Perform a Search and replace function.  Search for: [sk1] which is the
code that forces an unconditional blank line to be placed in a document.
Do not type anything in the Replace edit field.  The heading level 1
style contains an [sc1:0] code which places a conditional blank line
before and after the heading text.  The advantage with this code is that
if a heading appears at the top of a new page, the blank line that would
be placed before the heading text, is ignored.

When you have performed the Search and Replace functions, transcribe the
file into the braille output file.

Go to the Table of Contents Generator and select "Style to use:". Press
the <DOWN ARROW> to choose "custom".

Press the <SHIFT+TAB> key combination 3 times to move back to the "Use:"
combo box and press the <UP ARROW> to choose "Braille page numbers".
Then you can press the <TAB> key to go to the OK button and press
<ENTER> to start generating the table of contents.

By the way, the general rule is that, if a braille file does not contain
print reference page numbering, then the braille page numbers should be
placed at the top right hand corner of each page.

I would also point out, that it is not necessary to put braille page
numbers on even pages if the file is being embossed on an inter point
braille embosser.

I hope that the above information will be of help to you.

Sincerely:

Dave Durber


* * *
* 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
* * *

Other related posts: