The BSP supports contracted braille, uncontracted braille and computer braille code. It uses the Duxbury braille translator, but it isn't the same as the full-fledged version. I don't understand how different notetakers implement Duxbury, but the BSP uses an odd implementation. The program is trying to translate text into contracted braille and it's also trying to translate what you braille into correct text. That's why you will se a dot 4 dots 46 for a period when two initials are written with periods between them. This isn't proper braille, but you will notice it will backtranslate correctly. Instead of translating an underscore into dots 46, the BSP will use dot 4,456. It also adds dot 4 in front of a dash. If the dash is joined to a whole-word contraction, the whole-word contraction will be spelled out. This annoys me, so I put a space after the dash. I'm breaking a rule, but the braille is more readable. There are other oddities too: the BSP will usually add beginning cbc and ending cbc codes before and after an url or email address. It will also add a dot 4 in front of a greater-than sign. This is not a standard way to braille a greater-than sign. The apostrophe letter sign s is according to the new rules for writing some possessive words. The slash is supposed to be 456,34, but the BSP used 4,34, not right, but close. Anyway, you cannot change the way the BSP translates material. The only thing you can do is to edit the files to make them more readable. For example, you could remove all underscore signs. You can remove unwanted hard returns. I agree with you that the competition does a better job of its braille translation and its files are more readable.

Terri Amateur Radio call sign KF6CA.
If you wish to unsubscribe from this list, visit:

http://www.gwmicro.com/listserv

Reply via email to