prs
(The initial translation table for a translation is determined by the selected template, and may be changed using the Document / Translation Tables menu. Using those menus does not involve explicit use of the table designator. However, in cases where it is necessary to switch to a different translation table partway through a file, the designator for the table being switched to is required; see the general description of the [lnb~...] command for further details.)
The Dari tables support print-to-braille translation of Dari-language literary text into uncontracted Dari braille.
Uncontracted English is also supported. Technical (mathematics and computer) notation is generally transcribed as in Unified English Braille (UEB).
Although DBT Win 11.1 and later are able to display accented letter combinations and many non-Roman scripts, it is nevertheless often more convenient to use Microsoft Word for entering and editing print text, which can then be imported into DBT for subsequent translation. When preparing the text in Word, be sure to use a Unicode font (such as Lucida Sans or the default Times Roman), so that the underlying characters are encoded in Unicode. (Note that the appearance on screen is not the issue. Fonts that merely cause standard ASCII characters to be displayed as the desired accented or non-Roman letters will not work, because they will be imported according to their standard interpretation, not their appearance.)
True braille-to-print translation is not supported. This means that it is not generally useful to translate an Dari braille file to print. It also means that the "translated line" will typically contain gibberish when viewing the braille file. You may prefer to turn off the "translated line" under the View menu, or even under Global/Default if you wish it to be off by default.
Roman script is generally transcribed as in Unified English Braille (UEB).
There are no secondary languages supported within the Dari table itself; however it is possible to switch to any of the available translation tables listed in DBT. (See the [lnb~...] code below.)
Technical (mathematics, computer, or scientific) notation is generally transcribed as in Unified English Braille (UEB). It is also possible to switch to any of the available translation tables listed in DBT (see the [lnb~...] code below), many of which do support various technical codes, such as for mathematics or computer notation, or which support “unified” treatment of technical notation as well as literary text in the base language associated with the table.
The following DBT translation codes are available when using the Dari table. Codes related to the entry of type forms, mathematics, etc. as in the English/Unified tables may also be used and will generally be treated in the same way. Any other translation codes used will be ignored, or indeed may cause unexpected results. If using an alternative translation table, i.e when switching to another base language table by means of the[lnb~...] code, please refer to the relevant topic and available codes for that table.
[cz]
[lnb]
[lnb~...] (for switching to another base [primary] language table)
[tx]
The table is designed to work with the following groups of characters:
All ASCII printable characters
Letters and vowel marks used in Farsi
Accented letters and punctuation marks typical of French, German, Italian, and Spanish
British pound sign (£)
The above is a general guide only (see "General Notes" section under the main “Language Translation Tables” topic).
The rules for uncontracted Farsi were originally specified to Duxbury Systems by Mr. G. H. Shabani of the Braille Equipment Institute, Tehranpars, Iran, in cooperation with the Special Education Organization, part of the Iranian Ministry of Education. Work began on the tables in April 2005. More recent information has been provided by Mr. Amir Soleimani.
The tables for Dari are based on the existing Duxbury tables for Farsi.
(Documentation reviewed June 2010)