[duxhelp] Re: Request for input on DBT installation
- From: "Peter Sullivan" <peter@xxxxxxxxxx>
- To: <duxhelp@xxxxxxxxxxxxx>
- Date: Wed, 21 Jul 2004 15:02:15 -0400
Jack,
Yes, it's a pain. And we don't do anything in DBT to make this easier. Our
focus has been on documents that originate in DBT.
We do have some work in progress toward an easy-to-use encoding conversion
tool, but nothing ready to try yet.
- Peter
-----Original Message-----
From: duxhelp-bounce@xxxxxxxxxxxxx [mailto:duxhelp-bounce@xxxxxxxxxxxxx] On
Behalf Of Jack Maartman
Sent: Wednesday, July 21, 2004 12:34 PM
To: duxhelp@xxxxxxxxxxxxx
Subject: [duxhelp] Re: Request for input on DBT installation
Hi Peter:
This clarifies a great deal. I get the odd file from Europe, brailled in an
an alternate encoding, and have to do a complex set of search and replaces,
if I want to read it in my notetaker. I had hoped one could save a file in
a different encoding using DBT, without having to do this manually, or be
tied to a computer with a braille display. What worries me about all the
different braille computer tables, is the sharing of data across platforms.
It's a bit like having multiple charsets, and striving for some process like
unicode.
Jack
----- Original Message -----
From: "Peter Sullivan" <peter@xxxxxxxxxx>
To: <duxhelp@xxxxxxxxxxxxx>
Sent: Wednesday, July 21, 2004 9:08 AM
Subject: [duxhelp] Re: Request for input on DBT installation
> Jack,
>
> Internationalization is indeed for display purposes only. (OK, it does
> affect one other thing -- it affects what encoding we use when you select
to
> save a document as formatted braille using "local encoding".)
>
> One changes the codepage used to drive an embosser by using the the "Edit"
> button in the Embosser Setup dialog. Then go to the "Device Settings" tab
> (the second of three tabs). Choose a new value for the "Output Encoding"
> setting. We don't support alternate encodings for every device, but do
for
> the most common devices where this is even applicable. Moreover, in
> situations where we've neglected a possible setting that is supported for
> any given device, we can work with end users to make that setting
available.
> It's just a matter of editing one or two text files.
>
> - Peter
>
> -----Original Message-----
> From: duxhelp-bounce@xxxxxxxxxxxxx [mailto:duxhelp-bounce@xxxxxxxxxxxxx]
On
> Behalf Of Jack Maartman
> Sent: Wednesday, July 21, 2004 11:34 AM
> To: duxhelp@xxxxxxxxxxxxx
> Subject: [duxhelp] Re: Request for input on DBT installation
>
> Thanks Peter:
>
> However I am still a bit confused. I am almost certain, that the default
> configuration is supposed to be North American Ascii. At least I think it
> says so in the documentation. I thought the internationalization dialog
was
> for display purposes only. If you can clarify this for me It would kill
> more than a few birds with one stone.
>
> Thanks
>
> Jack
>
> ----- Original Message -----
> From: "Peter Sullivan" <peter@xxxxxxxxxx>
> To: <duxhelp@xxxxxxxxxxxxx>
> Sent: Wednesday, July 21, 2004 7:32 AM
> Subject: [duxhelp] Re: Request for input on DBT installation
>
>
> > Jack,
> >
> > By way of correction, embossing is by no means limited to the North
> American
> > table. DBT is adatable to any table that can express all 64 braille
> cells.
> > Moreover, it uses a different table by default for some embossers.
> >
> > We do this because some people use their embossers with other software
> which
> > isn't as flexible. We like to support use of the embosser without
> requiring
> > the end user to reconfigure it when switching software.
> >
> > - Peter
> >
> > -----Original Message-----
> > From: duxhelp-bounce@xxxxxxxxxxxxx [mailto:duxhelp-bounce@xxxxxxxxxxxxx]
> On
> > Behalf Of Jack Maartman
> > Sent: Tuesday, July 20, 2004 8:01 PM
> > To: duxhelp@xxxxxxxxxxxxx
> > Subject: [duxhelp] Re: Request for input on DBT installation
> >
> > Hi All:
> >
> > DBT defaults to North American by default. The display under the
> > international dialogue is only a display. No matter what, everything
still
> > has to emboss using the North American table. When you use the country
> > specific tables, they still refer to the North American ascii/unicode
> > equivalents. The problem here is that the actual braille characters'
ascii
> > values change, using North American as the default. The fault lies with
> > embosser manufacturers, who should design their tables in such a way
that
> > the braille patterns are reassigned to conform to the country for which
> the
> > table is needed. There is simply nothing Joe can do about this.
> >
> > I can't load DBT right now, but I am sure there is an uncontracted
Italian
> > braille table. Enabling technologies should have the Italian
> configuration
> > you need. If not, Brltty, the Linux engine that drives a braille display
> > should have one. As I write this, I have found one, which I attached. a
> > table for Window-eyes but it is a text file, even though the extension
is
> > .bwe
> > ----- Original Message ----
> >
> > Hope this helps
> >
> > Cheers
> >
> > Jack
> > :.
> >
> > Hope this helps
> >
> > Jack
> > -
> > From: "David Holladay" <david@xxxxxxxxxx>
> > To: <duxhelp@xxxxxxxxxxxxx>
> > Sent: Tuesday, July 20, 2004 1:00 PM
> > Subject: [duxhelp] Request for input on DBT installation
> >
> >
> > > Hello, Testers;
> > >
> > > I need you opinion on an issue regarding what happens when DBT boots
> > > up
> > for
> > > the first time.
> > >
> > > This involves the Global, Internationalization, Braille Code for
> > > Display
> > >
> > > Some background is necessary here.
> > >
> > > In DBT, if you are looking at a braille file in braille dot font, you
> > > see the actual dot pattern that will hopefully be embossed. If you are
> > > looking at a braille file with an inkprint font, things get more
> > interesting.
> > >
> > > In North America, we are used to seeing a full cell represented with
> > > an equal sign. Why? Because that is the way we do it, and all braille
> > > devices set for North American braille know that an equal sign means a
> > full cell.
> > > If you are using a braille display device with a screen review
> > > program,
> > the
> > > screen review program looks at the equal sign on the screen and puts a
> > full
> > > cell on the braille display.
> > >
> > > But in France, they prefer an accented e as the print representation
> > > of a full cell.
> > >
> > > DBT has several different tables. If you want to, you can experiment
> > > with them by selecting Global, Internationalization, Braille Code for
> > Display.
> > > Be sure to have a braille file, and select an inkprint font to view it
> > > (otherwise, nothing changes).
> > >
> > > -----------------------------------------
> > >
> > > Where things get interesting is that the French do not like the system
> > > as it is. Up till now, when you first boot up DBT, it defaults to
> > > North American. This does not bother Americans at all.
> > > But it is annoying to those who give tech support in France who have
> > > to keep telling people to go to Global, Internationalization, Braille
> > > Code
> > for
> > > Display, and then choose "French"
> > >
> > > To deal with this, Pete has put in some code that says "If this is the
> > > first time this code is being used, and you are in France", set for
> > > French Braille Code for display.
> > >
> > > That is all well and good. But if someone were using a computer 100
> > > meters into Belgium, (and had told Windows that their nation was
> > > Belgium), then DBT would still default to North American because the
> > > nation is not
> > French.
> > >
> > > ----------------------------------------
> > >
> > > I think it would be a good idea to extend Peter's idea. I offer a
> > proposal.
> > > If we can come to some agreement, then DBT can wake up more
> > > internationalized than before.
> > >
> > > ----------------------------------------
> > >
> > > Step 1:
> > >
> > > If located in France, use French display code If located in Germany,
> > > use German display code If located in Spain, use Spanish display code
> > > If located in the UK, use the British display code
> > >
> > > Step 2:
> > >
> > > If located in Europe (i.e. the nation's telephone country code starts
> > > with
> > > 3 or 4)
> > > and the language of interface is French, the use French display code
> > > and the language of interface is German, use the German display code
> > > and the language of interface is Spanish, use the Spanish display
> > > code ?? if the language of interface is English, do we use North
> > > American or Britich display code (the question is, does nayone outside
> > > of the UK ever use the British display code)
> > >
> > > Step 3:
> > > If located outside of Europe ...
> > > (I have no idea of anything but to default to North American) (I do
> > > not know if those in South America use North American settings or
> > > Spanish settings on their braille devices)
> > >
> > > Some of you may have noticed that DBT does not have any Italian tables
> > > for braille display. At this point, I do not have a valid table
> > > (defined as a unique, single ASCII character for every
> > > 64 braille symbols; no braille symbols left out).
> > > I would welcome a valid Italian table.
> > >
> > > ----------------------------------------------------------------------
> > > ----
> > -
> > >
> > > Please respond to this. I would like to work this out quickly.
> > >
> > > -- David Holladay
> > >
> > >
> > > * * *
> > > * 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 //www.freelists.org. The list archive
> > > * is also located there.
> > > * Duxbury Systems' web site is http://www.duxburysystems.com
> > > * * *
> >
> > * * *
> > * 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 //www.freelists.org. The list archive
> > * is also located there.
> > * Duxbury Systems' web site is http://www.duxburysystems.com
> > * * *
>
> * * *
> * 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 //www.freelists.org. The list archive
> * is also located there.
> * Duxbury Systems' web site is http://www.duxburysystems.com
> * * *
>
> * * *
> * 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 //www.freelists.org. The list archive
> * is also located there.
> * Duxbury Systems' web site is http://www.duxburysystems.com
> * * *
* * *
* 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 //www.freelists.org. The list archive
* is also located there.
* Duxbury Systems' web site is http://www.duxburysystems.com
* * *
* * *
* 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 //www.freelists.org. The list archive
* is also located there.
* Duxbury Systems' web site is http://www.duxburysystems.com
* * *
Other related posts:
