The phrase "file import" refers to taking a non-native DBT file and bringing it into DBT for editing and producing braille. There are many different file types that DBT can import. Of these, the most common is Microsoft Word.
If you want to import files into DBT for languages other than English, there are few alternatives beyond using Microsoft Word or Open Office. This topic is organized with all the information about file formats first, and all the information about languages other than English at the end.
The picture above is the File Open dialog. The pull-down menu near the bottom which shows All Files (*.*) allows you to see and select all different file types. When you open this menu, the first line is DBT Files (*.dxp, *.dxb) which are the native DBT print files (*.dxp) and braille files (*.dxb). Because this is a discussion about importing files from non-DBT sources, we omit discussion of the native DBT files.
Opening a non-native file in DBT presents the File Import dialog. You can see what this dialog looks like in the File: Open topic.
Note: This section deals with files written in the English language.
Duxbury DBT has supported Word 97/Word 2003 files for a very long time. From DBT version 11.1 (2011), DBT has supported importing Microsoft Word 2007/2010 files. More recent versions of DBT import Word 2013/2016 files. If you have an older version of Duxbury DBT, you need to update to import these important file types.
Open Office is an open source alternative to using Microsoft Office. Open Office uses a similar file format to Word 2007/2010. If you have Duxbury DBT 11.1 or newer, you can also import Open Office files.
For those preparing files for use in the United States, a template for MS Word comes with DBT to ease the work of braille production. Click here for details on the latest BANA Template.
MathType is a relatively low-cost program which, among its many capabilities, enables mathematical equations to be inserted into Microsoft Word documents. It is produced by Design Science, Inc.. Word documents containing MathType equations can be opened in DBT, and translated into mathematical braille. See below about Scientific Notebook, another popular program for producing math equations for use with DBT.
DBT does not directly import MS Word RTF files. Many third party programs produce RTF files but call them Word Documents. Some versions of Adobe Acrobat offer to export to Word files. Some OCR software offers to produce Word documents. In both cases, the result may actually be an RTF file. See below on how to convert RTF files into true Word files.
If you do attempt to import an RTF format file into DBT, DBT posts an error message, identifying that this is an RTF file.
While WordPerfect is not a leading product anymore, it was once the premier word processor. DBT retains the ability to import files from WordPerfect 3.x, 5.x, and 6.x.
DAISY files (Digital Accessible Information SYstem) are XML files designed for access by the disabled. While useful for braille production, DAISY files often lack all of the encoding needed for quality braille. While DBT can import these files, some of them are extremely large, making direct import difficult.
NIMAS files are specialized DAISY files which meet national instructional materials standards. These files are often massive, and they can require careful treatment to prepare them for braille. Duxbury Systems has created a program called NimPro, which greatly facilitates the import of NIMAS files to DBT. Please, see our Web Site for more information.
Getting quality braille files from MegaDots to Duxbury DBT has become quite easy. MegaDots 2.5 can export a file from MegaDots into the MegaDots export file type MS Word/BANA Template. This file can be imported into DBT using the DBT template English - American - BANA. Just about all the subtle formatting placed in the MegaDots file is carried over into the DBT file, so it is worthwhile to follow the recipe exactly.
DBT imports many different standard text (.txt) files.
Modern text files mostly use the "Unicode" character set, but older files may use one of many "Code Pages" to represent their text. If you find yourself facing unreadable text, selecting the correct Code Page may help. See DBT Code Pages for Text Files.
Scientific Notebook, is software which produces LaTeX files. LaTeX files can be imported into DBT both for the text and the mathematical equations. (See above about MathType, another popular program for producing math equations for use with DBT). Duxbury Systems supports Scientific Notebook 5.5, which is still available as a download. The new version, Scientific Notebook 6.0, is not compatible with DBT at this time.
DBT has the ability to import simple HTML files from the web. If the direct file import is not successful, import the HTML file into Microsoft Word, then export (Save As) as a native Word file. NOTE: Word offers as a default choice to export the file back into a Web Page. You need to deliberately select Word file as the file type to import this file into DBT.
To import an RTF file into DBT, first import the file into Microsoft Word, then export (Save As) as a native Word file. NOTE: Word offers as a default choice to export the file back into a Rich Text Format (RTF) File. You need to deliberately select Word file as a file type. Then you can import this (actual) Word format file into DBT.
Braille Formatted Files are not all alike, nor should they all be imported the same way. The primary variations to consider are BRF files that were encoded in UEB versus those encoded in Pre-UEB. Further, the manner of import depends on whether you intend the file only for embossing, or you need to edit the text. Click here for a detailed discussion on importing braille formatted files.
DBT supports Unicode fonts. Microsoft Word works with both Unicode and non-Unicode fonts. In the past, languages like Lao, Tibetan, or Oriya were impossible to support without specialized add-ons to Microsoft Word. It is now possible to buy a computer, obtain a word processor (Open Office or Microsoft Word), and immediately set to work writing in many alternate script languages without first having to obtain a special font. As an added bonus, this means that screen readers and other accessibility software have more opportunity to handle your language. At this point, DBT imports or handles about 75 ranges of Unicode characters.
For some nations, their isolation from mainstream computer users and the cost barriers to better solutions caused widespread use of non-Unicode fonts. Thus to offer a braille translator that is practical, Duxbury Systems had to support the dominant font system in use. We have some support for the Akadem font for Cyrillic text, the Saysettha font for Lao text, and the SutonnyMJ font used in Bangladesh for Bengali text.
This work is exacting and quite complex, so Duxbury supports non-Unicode fonts only when there are no other alternatives.
DBT does not directly display Chinese characters. Instead DBT displays an appropriate substitute based on the current braille translation language:
| Language | DBT Characters |
|---|---|
| Mandarin (Mainland) | Pinyin romanization with accent marks for the tones |
| Mandarin (Taiwan) | Zhuyin romanization |
| Cantonese | Jyutping romanization with superscript numbers for the tones |
| Japanese | Unicode U+30xx characters |
| Korean | Unicode U+11xx characters |
In the Global Settings, Word Import Menu, you can set the choice of how Chinese characters are imported.
Both Arabic and Hebrew inkprint are written from right to left. Arabic and Hebrew braille are written from left to right. While DBT displays all inkprint text from right to left, do not attempt to edit the text in DBT. Instead, clipboard the entire line into Word, edit it in Word, and then paste the whole line back into DBT. See also the note below about Script and Font Issues.
Hangul script composes 2 or 3 characters into a single symbol. When DBT imports a file, the process is reversed. DBT breaks down a single Hangul character into its component parts. In technical terms, all Hangul characters from U+AC00 through U+D7AF are redirected into Hangul Jamo characters U+11xx. The result can be difficult to read for those who are used to reading the conventional inkprint. For these languages, it is best to do all the editing in Microsoft Word, then to import into DBT and use DBT as the translation engine and for output.
In many countries, the Windows XP operating system still plays a significant role despite the fact that it is no longer supported. Many scripts are difficult to support on Windows XP.
Many scripts (Mandarin, Cantonese, Ethiopic, Khmer, Lao, Oriya, Sinhala, and Tibetan) are best viewed on a Vista, Windows 7, Windows 8, or Windows 10 machine.
Myanmar (Burmese) script support requires Windows 8 or Windows 10.