A translation table is a module in DBT that provides the rules to convert (translate) a document from print-to-braille or from braille-to-print. Normally, it is selected by the DBT template that controls production of the current document. All documents have a template. In fact, for many languages there are multiple templates, with differences in translation rules or formatting, but each references at least one translation table. (For more on templates, see DBT Templates, the Basics.)
Regardless of your template, you can choose a different translation table to translate your current document using the Translation Table selection from the DBT Document Menu.
You can also select different translation tables to use for particular passages in your document. See the section below on Language Table Switching.
The Haryanvi tables support print-to-braille translation of Haryanvi-language literary text into uncontracted Haryanvi braille. Any of the scripts generally used in India and surrounding regions: Arabic (including Sindhi), Bengali, Devanagari (Hindi), Gujarati, Gurmukhi, Kannada, Malayalam, Myanmar, Oriya, Sinhala, Tamil, or Telugu, may be used for print-to-braille translation. Roman script generally is translated as uncontracted braille (with English assumed).
Translation from braille-to-print is supported for this language.
Table Designator: bgc identifies this translation table for Language Table Switching.
Braille Contractions: This language is usually produced in uncontracted braille. This means that the letters of each word are rendered into braille on a one-for-one basis.
Capital Sign: The Haryanvi translator does not use any capitalization mark in braille because the native script does not employ capitalization. Text written with the Roman alphabet (such as English) uses dot 6 for capitalization.
Emphasis: The Haryanvi translator ignores all bold, italics, and underlining from the inkprint text. These are not represented in the braille.
Mathematical Braille: With Haryanvi, you have a choice of two DBT templates. One uses UEB Math, the other uses Nemeth Math.
Script Systems Used: The Haryanvi translator handles all of the scripts of India (U+0900-0DFF), Arabic (U+0600-06FF), and Myanmar (U+1000-1059). The Haryanvi translator also handles text using Roman characters, and a wide variety of symbols and punctuation marks.
The Haryanvi translator is closely related to all of the translators used for the languages of India, Nepal, Myanmar, and Sri Lanka. All of these translators share a common set of features and capabilities for translating from print-to-braille. Note, however, that each of the major scripts has its own braille-to-print translator. You do not need to use language table switching to mix different Indic scripts for print-to-braille translation. You do need to use language table switching to mix different Indic scripts for braille-to-print translation.
A number of DBT codes affect the mode of the translation or create special translation effects on specific letters or symbols. Some translation modes are specific to particular translator tables.
There are no special translator modes for this table, only those which are present for all tables, such as the [lnb~] code (language-switch) and a few codes for internal testing.
For more about DBT codes that affect the mode of translation, search on the two words, "Translation Code", in the topic, DBT Codes Quick Reference.
Duxbury Systems, Inc. originally implemented these tables in April 2008, based upon several sources: the document, "World Braille Usage," a joint publication of UNESCO and the National Library Service for the Blind and Physically Handicapped, Washington, D.C. (1990), as well as information posted by two organizations in India, Acharya (IIT Madras) and Baraha, a developer of software for Indian script editing.
Notice that if you include Roman alphabet characters in a document but do not use a language style or code to switch to a different translation table, you will get uncontracted English with the same marks of punctuation, emphasis, and capitalization used for the base language.
Duxbury Systems, Inc. originally implemented these tables in April 2008, based upon several sources: the document, "World Braille Usage," a joint publication of UNESCO and the National Library Service for the Blind and Physically Handicapped, Washington, D.C. (1990), as well as information posted by two organizations in India, Acharya (IIT Madras) and Baraha, a developer of software for Indian script editing.
Duxbury Systems is grateful to Mr. Dipendra Manocha, Mr. J. L. Kaul, and their colleagues in India who helped us greatly by expanding upon that original information, conducting tests, and providing feedback.
If you have information about changes in the braille rules for your language, please email Duxbury so that we may update our translation tables. Likewise, if you find errors in your translated document, in either the print-to-braille or braille-to-print direction, please contact us. To describe your problem, it is best to send both the *.dxp and *.dxb files along with a full explanation, because the correct braille is often a matter of very specific circumstances. Contact Duxbury at: languages@duxsys.com.