[duxhelp] Re: Request for input on DBT installation
- From: "Jack Maartman" <jmaartman@xxxxxxxxxxx>
- To: <duxhelp@xxxxxxxxxxxxx>
- Date: Wed, 21 Jul 2004 15:46:54 -0700
Hi David:
I'd love a copy of the program. I'd hazard a guess, albeit off the wall,
that you might contact the Italian Braille authority, or it's equivalent.
Highly interested in your assertion about the Blazie notetakers. As one who
works exclusively with eight-dot braille, you can't represent all 256
eight-dot braille patterns, on an "FSnotetaker, and what gets left out is
arbitrary, or so it would seem.
By the way, and you should probably reply off list, how does Megadots handle
this. I know nothing about it, got a research license from Duxbury, and
don't own an embosser, but for a long time I have been interested in
Megadots. When Joe gave me the license, I didn't have the temerity to ask
for the bundle. Sorry for taking up list time with this one.
Cheers
Jack
jmaartman@xxxxxxxxxxx
----- Original Message -----
From: "David Holladay" <david@xxxxxxxxxx>
To: <duxhelp@xxxxxxxxxxxxx>
Sent: Wednesday, July 21, 2004 3:34 PM
Subject: [duxhelp] Re: Request for input on DBT installation
> Jack:
>
> Thanks for your help on the Italian codes. As an 8 dot code it had problem
> (many duplications).
> For our purposes, we do not care about duplications. We do care about
> ommisions, and your list did not have
> dots 235.
>
> It did inspire me to go over all the Italian data I did have, and I
noticed
> that it was quite similar to a table
> I got from Braillo in Norway, in a file called ita039-02.txt (039 being
the
> telephone code for Italy).
> I ignored it before, since it was the "02" code (presumably not the
primary
> code for the country). Since it
> was so similar to the one you sent, I went over it carefully. It has all
> braille cells when just using 6 cells.
> Just for completeness, I am giving it in two forms, .cpa is in ASCII
order,
> and .cpt is in braille dot order.
> (By the way, I can e-mail anyone a copy of the program I wrote that
> converts from cpa to cpt)
>
> BTW Enabling does not have a good Italian encoding, I have already talked
> to them several times.
>
> You will notice that DBT 10.5 makes the different encodings available when
> sending to an embosser, only if
> that embosser contains that encoding.
>
> I have heard rumors that the Braille 'n Speak has 28 different encodings,
> but no one has a copy of these that they
> can send me.
>
> The attached file (when truncated to only 6 dots) is my proposal for an
> Italian braille display code. Anyone with any
> objections should e-mail me as soon as possible.
>
> -- David Holladay
>
>
> At 05:00 PM 7/20/2004 -0700, you wrote:
> >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
> >> * * *
> >
> >Attachment Converted: "C:\TDSNET\EUDORA\Attach\italian8.bwe"
> >
* * *
* 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:
