[duxhelp] Re: FW: Re: First braille line after print page indicator is indented two cells in .brf files

  • From: Susan <chrn3292@xxxxxxx>
  • To: duxhelp@xxxxxxxxxxxxx
  • Date: Sat, 28 Aug 2004 13:33:28 -0500

J.R. is using the BANA template, which treats the [lea] differently than 
  other DBT templates. When using the BANA template, the runover of the 
style is honored after inserting a new page number mid-paragraph ... 
however the number MUST be followed by a space.

Right now, the file has

      I [lea]4[l] still


Use a space after the number

      I [lea]4 still

and everything will be OK. Using [l] within a BANA template style is 
similar to using Ctrl-M ... however, instead of creating a new paragraph 
with its own set of style codes, it creates a new paragraph WITHIN the 
SAME style codes. That's what happened here ... it was just coincidental
that it was after the page number.

Susan




George Bell wrote on 8/27/2004, 7:19 PM:

Hi J.R.  (And sorry for the attachments being
added here, but I'm copying this to Peter & Joe)

And sorry also  re my earlier message, but I found
I needed to look at this before I slept.  So I
could still be wrong in what I believe I have
found.

Unfortunately you didn't attach the Word file, so
this is much of a guess.

Basically,  it appears that there is a Style in
the original document called "B-BodyText".

This is a Custom Style, and not mapped in the MWS
file.  So, it gets brought into DBT - as is - so
to speak.

If you change that Style to "para.", you don't get
the indent.  Obviously DBT's inner workings
recognise the [lea] code within the "para." Style,
and so deal with it as you would expect.

As to a solution, and again without the original
file I'm largely guessing, but could you perhaps
try:-

1)  Mapping "B-BodyText" to "para" in your MWS
file, or....

2)  Use SWIFT to do the mapping of Custom Styles
for you.

I have to confess that I am a shade worried about
Custom Word Styles coming into DBT in this way.
In some ways it is good, and personally as a,
"Styles Man" I really like it.  However, I suspect
it may cause some confusion unless SWIFT is used
properly.

All the best,

George.

________________________________

From: duxhelp-bounce@xxxxxxxxxxxxx
[mailto:duxhelp-bounce@xxxxxxxxxxxxx] On Behalf Of
Westmoreland, J. R.
Sent: 27 August 2004 23:33
To: duxhelp@xxxxxxxxxxxxx
Subject: [duxhelp] Re: First braille line after
print page indicator is indented two cells in .brf
files


George,

Here are the two files attached.
1) a .dxp file with 6 print pages showing the
problem.
2) the .brf file after translation.

Let me know what you discover.
Don and I are doing further testing as well and
I'll let you know what we find.

Thanks,
J. R.



______________________________
J. R. Westmoreland
PacifiCorp
I/T
Telecomm Data Communications
Phone: (801) 220-4784




________________________________

From: duxhelp-bounce@xxxxxxxxxxxxx
[mailto:duxhelp-bounce@xxxxxxxxxxxxx] On Behalf Of
George Bell
Sent: Friday, August 27, 2004 1:41 PM
To: duxhelp@xxxxxxxxxxxxx
Subject: RE: [duxhelp] First braille line after
print page indicator is indented two cells in .brf
files


Hi J.R.,

Can you provide a small actual example?

What Template is this with?  (I've just tested
with the Standard Literary Template)

FWIW, I do a Ctrl + [, type lea, and press enter.
Then I type the page number followed by a space,
and continue with the text.

Are you by any chance pressing Return after
entering the print page number?

Sorry if I am asking the obvious, but it's tricky
to tell what's happening without seeing an
example.

All the best,

George.

________________________________

From: duxhelp-bounce@xxxxxxxxxxxxx
[mailto:duxhelp-bounce@xxxxxxxxxxxxx] On Behalf Of
Westmoreland, J. R.
Sent: 27 August 2004 17:41
To: duxhelp@xxxxxxxxxxxxx
Subject: [duxhelp] First braille line after print
page indicator is indented two cells in .brf files


I'm running the latest beta release and this
problem is causing me major fits.
Is there a work around for it?

The two spaces are not shown in any of the files
except after saving as a .brf file
There is not even a way to edit these out except
by editing the .brf file after translation.

J. R.


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