This is the technical description of a DBT Translation table. If you want more general information about languages and template choices, please see the list of templates.
Initially, the language table for braille translation is determined by the selected template, and may be changed using the Document / Translation Tables menu. Using those menus does not require 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 Croatian tables support print-to-braille translation of Croatian-language literary text into contracted or uncontracted Croatian braille.
Braille-to-print translation is supported for this language. However, braille-to-print translation may not be perfect, therefore beware that errors can occur. If you find errors or have suggestions, please send both the *.dxb and *.dxp files along with an explanation to: firstname.lastname@example.org. Please be sure to include sample files!
Although DBT Win DBT 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.)
There are no secondary languages supported within the Croatian table itself; however it is possible to switch to any of the available translation tables listed in DBT. (See the [lnb~...] code below.)
No technical braille codes are supported directly within the Croatian table itself. However, it is 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 Croatian table.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.
[ii] -- produces dot 6, otherwise ignored
[lnb~...] (for switching to another base [primary] language table)
The table is designed to work with the following groups of characters:
All ASCII printable characters
Accented characters and punctuation marks typical of Croatian, French, German, Latin, Spanish, Portuguese, and Finnish. Although Croatian letters are basically from the Roman alphabet, certain letters may be modified with a stroke, caron or acute accent. Precomposed Unicode characters, when available, may be used for these modified letters, or the markings may be added to the ordinary letter by entering the applicable "combining" Unicode marks immediately after the basic letter.
British pound sign (£)
The above is a general guide only (see "General Notes" section at the beginning of this document).
These tables are based upon the information on Croatian and related languages in "World Braille Usage," a joint publication of UNESCO and the National Library Service for the Blind and Physically Handicapped, Washington, D.C. (1990) and also information provided by Ms. Lucia Guderzo of Tiflosystem S.p. A. (Italy).
The tables were originally developed beginning in November 2005 by Duxbury Systems, Inc.
(Documentation reviewed May 2010)