bod
This page describes the internal functioning of the respective DBT translation table. If you want more information about languages, scripts, and template choices, please click here.
The initial language 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, to switch to a different translation table partway through a file, one must enter a DBT code and the designator for the table to switch to. For switching secondary languages within a base language table, see the [lng~X] command. For switching from one base language to another, see the [lnb~...] command.
The Tibetan tables support print-to-braille translation of Tibetan-language literary text into uncontracted Tibetan braille.
Uncontracted English is also supported. Technical (mathematics and computer) notation is generally transcribed as in Unified English Braille (UEB).
Braille-to-print translation is supported for this language. However Braille-to-print translation may not be perfect, therefore errors could occur. If you find any errors or have suggestions, please send both the *.dxb and *.dxp files along with an explanation to: languages@duxsys.com (Please be sure to include sample files).
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.)
Roman script is generally transcribed as in Unified English Braille (UEB).
There are no secondary languages supported within the Tibetan 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 Tibetan 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
Tibetan letters and punctuation marks
Mathematical signs, shapes, etc. (DUSCI pages D+df..., D+e2..., D+e5..., D+ef..., D+f0..., D+f1...)
The above is a general guide only (see "General Notes" section under the main “Language Translation Tables” topic).
The Tibetan Braille Translator is based on spreadsheets and pdf files provided by Braille Without Borders. Working with Braille Without Borders, we also included handling of the popular Wylie Romanization. We welcome comments to improve these tables.
(Documentation reviewed June 2010)