[duxhelp] Re: word documents related problems

  • From: Jean-François Colas <jfcolas@xxxxxxx>
  • To: duxhelp@xxxxxxxxxxxxx
  • Date: Fri, 03 Dec 2004 10:38:51 +0000

Hello Anita & All,

Concerning your first question, I would like to suggest you to uncheck everything about automatic replacements in Word, and particularly those concerning quotes or double quotes. You will probably find them in the Tool menu, after that I can't be sure of the item names, having a french version of Word. Something like "Automatic replacements", in which you will find a page about "during typing").

J.-F.

Message de Anita Munshi, à 23:27 02/12/04 +0100
Hello Peter:

I love the explanation you have given to some of the codes asked by one of the user of DBT. I know you are travelling, but I didn't want to forget abot this problem. I also have a sample file so I thought of writing this email now. You can get back to me when you get time.

Two things:

One we sometimes need to create braille dots or simbraille dots in Word using the braille font. Two dots we cannot get to work is dot 3 and dot 5 - (which is an apostrophy and a double quotes in ASCII). Every other contraction works (at least the ones I have tried). Do you know what the reason for this is. This is required when we create a print manual and need to give braille examples. Right now of course I create the dots in DBT, copy them into word and change the font to braille. Is there a way to make Word recognize these dots and get a dot 5 and a dot 3 to work.

Second problem I have reporte many times. Lot of headings that are upper caps or fully cap words in Word import into DBT either as Initial caped letters or no caps at all. And if I am not paying attention to all the headings and mini headings, I get a long sheet of errors. Attached is a file which gives you perfect examples. I imported it into DBT 10.5 and you can see the results, most Double Caps have been dropped. Is there a solution for this?

Your help is very much appreciated.

Anita Munshi

-----Original Message-----
From: Peter Sullivan [mailto:peter@xxxxxxxxxx]
Sent: Thursday, December 02, 2004 2:20 PM
To: duxhelp@xxxxxxxxxxxxx
Subject: [duxhelp] Re: Several questions about some codes


Hello Pascale,

I do have time for one message before my flight out.

[lps] and [lpr] are useful for creating certain biblical formats in which
verse numbers are shown in several cells reserved along the left edge of the
page.  Text beyond the space on the left wraps normally.  A DBT user can
create the desired wrapping by setting a left margin, using the [ind]
command.  Then, the only problem is getting the verse numbers back to the
left edge of the page, well to the left of the left margin.  For this, it is
typical to use [lps] (to save the current place on the page), then [taa1] to
"zap" to the left edge of the page.  After typing the verse number, [lpr] is
used to return to the spot where the next word in the text should be.

Guidewords are words typically found at the top or bottom of a dictionary
page.  The guideword on the left page matches the first entry on that page.
The guideword on the right page matches the last entry on that page.

An "anticpatory page number" is that page number which matches the print
page corresponding to the text at the end of a braille page.  In Australia
and, I believe, the UK, even when print page numbers are shown at the top of
a braille page, they should correspond to print page number for the text at
the end of that page.

The paramters to [vcs] (M:N) are difficult to understand.  Fortunately, they
are not often needed.  To understand them, it is simplest to think of them
as a fraction N divided by M.  So [vcs2:1] could be read as "vertical
center, one-half".  The one half means that the space before the text on
this page will be one-half the of the total count of blank lines.  Likewise
[vcs3:1] (or "vertical center, one-third" means that one-third of the blank
lines will be above the text (two-thirds will be below).  To flip these
proportions, you would use [vcs3:2], so that two-thirds of the blank lines
will be above the text, and one-third will be below it.  Leaving the
parameters out altogether is just like using [vcs2:1], so the text will be
vertically centered.  Using [vcs1:1] aligns all of the text at the bottom of
the page, because all blank lines are placed above the text.

George may be in touch with further details.  (Thanks for jumping in,
George!)  I won't be available for at least the next twenty-four hours.

Best Regards,

Peter

-----Original Message-----
From: duxhelp-bounce@xxxxxxxxxxxxx [mailto:duxhelp-bounce@xxxxxxxxxxxxx] On
Behalf Of Pascale ISEL
Sent: Thursday, December 02, 2004 11:21 AM
To: duxhelp@xxxxxxxxxxxxx
Subject: [duxhelp] Several questions about some codes



* * * * This message is via list duxhelp at freelists.org. * To unsubscribe, send a blank message with * unsubscribe * as the subject to <duxhelp-request@xxxxxxxxxxxxx>. You may also * subscribe, unsubscribe, and set vacation mode and other subscription * options by visiting http://www.freelists.org. The list archive * is also located there. * Duxbury Systems' web site is http://www.duxburysystems.com * * *

Other related posts: