Global: Formatted Braille Importer...

Keystroke: b from Global menu

See also: BRF files - Importing

See also: BRF files - Importing in the on-line Help.

Image shows the Global: Formatted Braille Imported dialog described here.

Note: To open a .brf file in DBT, please use the normal File: Open command.

The Formatted Braille Importer dialog is used to inform DBT about the dimensions and page numbering conventions of the BRF format braille files you wish to import. DBT can import BRF files from older DBT versions, as well as PokaDot files and other formatted braille files. Note that DBT use the settings in this dialog for import analysis only. In other words, after the import is complete the incoming file will be reformatted to the dimensions set in the Global Embosser Setup dialog or template, using the numbering scheme set in the Document Menu, not in its original format as described here.

There are 11 Controls in this dialog.

The Check BoxCheck Box, Read formatted braille without interpretation. When this is checked, most of the other controls on the dialog are disabled.

Next are two groups of Radio ButtonsRadio Buttons to tell DBT in what corners it can expect to find braille page numbers on even and odd pages, respectively.

The next two radio button groups work the same as the first two, but they refer to the print page, as used in Textbook braille format.

Next are two additional radio button groups in which you can tell DBT where it will find running headers and running footers, respectively.

The final two controls are text fields to tell DBT the dimensions, in characters, of the formatted ASCII braille file. The lines per page is a maximum value (which should be set higher than the actual format) while the cells per line should be set for the exact width of the pages in your BRF, or equivalent, file.

Note: By their nature, formatted (ASCII) braille files are stripped of all format and translation codes. To get the file ready for editing, DBT interprets the format and adds codes accordingly. Because an interpretive process can go wrong, we recommend, whenever possible, that you use the source TXT or WP file instead of the BRF for importing.