[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Registration of new charset BRF
Hello Samuel,
Many thanks for your inquiries with Duxbury.
Why don't you include both the Wikipedia and the Duxbury
link in the registration? Also, please put the expanded
name of the encoding in the 'Additional Information' section.
Regards, Martin.
At 16:10 06/10/05, Samuel Thibault wrote:
>Hi,
>
>Martin Duerst, le Mon 02 Oct 2006 16:38:22 +0900, a 馗rit :
>> >Published specification(s):
>> >
>> >http://en.wikipedia.org/wiki/Braille_ASCII
>>
>> This does not look like the actual specification
>> (e.g. by ISO/IEC, a national standards organization,
>> or so), but looks more like a document about the encoding.
>> Is an original specification (e.g. on the Duxbury Web site)
>> available?
>
>I got an answer from Duxbury:
>
>ォ The short answer is that there is no official standard for the BRF
>format. Our company's best braille expert offered some more information
>about the subject:
>
> If "official" means an ISO standard, then there is none. However, though
> defined by Duxbury many years ago (1975), BRF files are widely understood
> and accepted in the industry and community concerned with braille, as a
> simple and obvious way to encode any arbitrary document consisting entirely
> of standard 6-dot braille text, regardless of content or format. It is in
> that sense a defacto standard. For the many braille embossers that are
> designed to operate like a classic "teletype" printer, a BRF file can often
> serve as an embosser-ready file -- i.e. it can be sent directly to the
> embosser without any intervening processes apart from those essential to
> driving the hardware itself. That use, in fact, was the basis of the
> definition of BRF files in the first place.
> A BRF file is very simply defined:
> Each character in braille is encoded according to the North American
> ASCII-Braille code, sometimes called the MIT code (from its genesis in the
> 1960s) and also known as the North American Braille Computer Code or NABCC.
> For example, a space (no dots) is an ASCII space, dots 14 is an ASCII 'c'
> (or 'C' -- case is irrelevant), dots 126 is an ASCII '<'. The complete set
> of equivalences is listed in the table towards the end of
>
> http://www.duxburysystems.com/braille.asp
> サ
>
>I'm not sure know whether the url above will be as "stable" as the
>wikipedia one, however.
>
>Samuel
#-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-# http://www.sw.it.aoyama.ac.jp mailto:duerst@it.aoyama.ac.jp