Hi guys,
In my case, I put dots 5-6 before a lone letter like what the
originator has described on print version. However, when the
back translator is invoked, the "s" in parenthesis would be
treated as "so" sign, thus putting a letter sign with back
translation in mind. As Mike said, computers cannot emulate all
the BANA rules that were laid down several decades ago, thus the
existence of the resolver operator (the letter sign) to
distinguish the letter from an actual contraction. Also, it is
hard (somewhat from a programmer's perspective) to implement back
translation algorithms for all possible scenarios (which I
understand where the originator is going at), particularly with
specialized devices such as Br Sense family and others.
I can tell you this: Korean is harder to script than English,
although in back translation, it is easier. English uses ASCII
for keyboard command macros, whereas Korean uses a combination of
ASCII and unicode set for Korean alphabet. The eight-dot
combination of the braille keyboard set would allow all 256 ASCII
combinations (including the extended ASCII set for a total of
2048 bits). However, because of the nature of the language,
Korean braille requires up to three or four braille cells to
represent a single letter (the consonants surround the vowel for
majority of the Korean words). If we write the Korean name of
this family (Hansone, pronounced "Hahn-Soh-Nae" meaning in "one
fingertip"), it would take six cells (two for each of the
letters). When it comes to translations, because each braille
symbol corresponds to either a consonant, vowel or a punctuation
in Korean (apart from one-letter contractions), it would be
easier to look up the translation tables array (come to think of
them) and translate them that way. However, with English, we
have several single letter contractions such as "but", "can",
etc. In order to help the back translator, it would be wise to
put the letter sign to allow the next letter to be treated as a
single letter, as explained earlier.
Well, hope it explains a few things here... BTW, the condition
that the originator has laid out also affects other devices such
as the Apex.
Cheers,
Joseph
----- Original Message -----
From: "Mike Freeman" <[email protected]
To: <[email protected]
Date sent: Sat, 8 May 2010 14:21:56 -0700
Subject: Re: [GWN] Suggestion for a future release
Omitting the dot 4 might work OK for reading but not for writing.
Computers
are emphatically *not* paper braille.
Mike
----- Original Message -----
From: "Olusegun -- Victory Associates LTD, Inc."
<[email protected]
To: <[email protected]
Sent: Saturday, May 08, 2010 2:13 PM
Subject: Re: [GWN] Suggestion for a future release
Raul, I beg to differ. the BSP is NOT following any BANA rules.
Why
would BANA suggest that a space come between the word whose
example I
cited? I suggest you read the word again using one character at
a time:
The word Item(s) on the BSP is spelled item (dot 5-6s). That is
ABSOLUTELY WRONG. There need not be a space between the M and
the OPEN
PARENTHESIS, and most certainly no need for dots 5-6 before the
S after
which there is a closing parenthesis.
If as I stated this is a BANA rules, it is a ridiculous one at
best. As
for UEB, I don't want it, but I do want Standard English
Braille. I don't
need the extra dot 4 before an before dots 3-4 for the slash
character.
In general, I don't export any document I produce on the BSP
anywhere. It
is for my own uses and I want to have control over how I want
the
charactrs displayed on my Braille Notetaker.
Sincerely,
Olusegun
Denver, Colorado
If you wish to unsubscribe from this list, visit:
http://www.gwmicro.com/listserv
If you wish to unsubscribe from this list, visit:
http://www.gwmicro.com/listserv
If you wish to unsubscribe from this list, visit:
http://www.gwmicro.com/listserv
