Afrikaans (Pre-Unified) - Translator Table
Table Designator: afr-x00
Advisory: This braille translator is obsolete. The governing braille authority has introduced a newer braille code that replaces this one. Those familiar with this older code might have reason to want it for personal use. However, Duxbury recommends that braille produced with this translator should not be used for any official purpose, whether educational, governmental, commercial, or any form of outreach to blind individuals, unless specifically requested by the blind individual in question.
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.
Purpose
The Afrikaans (pre-Unified) tables support print-to-braille translation of Afrikaans-language literary text, in either contracted (grade 2) or uncontracted (grade 1) braille, according to the code in effect prior to the introduction of Unified Afrikaans Braille in 2010.
Translation from braille to print is not supported for this language. If you would like Duxbury Systems to prioritize the creation of a braille-to-print table for this language, please contact languages@duxsys.com.
Key Characteristics
Table Designator: afr-x00 identifies this translation table for Language Table Switching.
Braille Contractions: This language is usually produced in contracted braille, which means one should not expect a one-to-one correspondence between inkprint letters and braille cells. Instead, abbreviations (contractions) are used for many common words and letter sequences.
Capital Sign: uses dot 6 as the capital sign.
Emphasis: The translator converts all forms of emphasis in inkprint (bold, italics, and underlining) to a single braille emphasis marker, dots 456.
Mathematical Braille: If you use the recommended DBT template with this translator table, you can access the UEB Braille mathematics translator by using the math Style.
Script Systems Used: The translator handles Roman characters, and a wide variety of symbols and punctuation marks.
Translation Modes (DBT Codes which Change the Mode of 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.
[g1] switches to grade 1 as the "prevailing grade", but does not insert a grade 1 indicator.
[g2] resumes grade 2 as the prevailing grade, but does not insert a grade 2 indicator. (Grade 2 is the normal prevailing grade.)
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.
Language Table Switching
DBT has translation tables for over 200 world languages. Modern versions of DBT allow using multiple language translation tables within a single document.
Suppose that you are working on a document using this base translation table, but it has passages in a foreign language, or that need a technical braille code. At the beginning of each such passage, insert the DBT code lnb, followed by ~ (tilde) and the table designator for the desired language table. (The table designator for each language table is listed in the Key Characteristics.) Note that using the lnb code you can change from the base table to virtually any other translation table and back again.
For some language tables, the table designator is short, like ise for Icelandic. Thus, to switch to Icelandic braille translation, insert [lnb~ise]. The table designators are more elaborate for mathematics code tables and for languages that have multiple translation tables. As an example, the designator for Unified French Braille is fra-xuf. To start a passage in the French Unified Braille code, insert [lnb~fra-xuf]. At the end of a foreign language passage, use the plain [lnb] code to switch back to the original, base, language translation table.
Some translation tables, and hence their table designators, are for braille codes but not for natural languages. Some examples are the International Phonetic Alphabet (designator: qip) and Nemeth Code (designator: qmt-xnem72m) for mathematics. Using lnb with those table designators allows you to switch to the IPA braille code or the Nemeth braille math code.
While a plain [lnb] code returns translation to the base language, it does not restore any other translation properties that might have been in effect before the switch. For example, if you had been using a [g1L] code (for "grade 1 lock") to prevent contractions, you need to repeat that code after the [lnb] code to restore that effect. Fortunately, you can build lnb codes into DBT styles, to customize what modes to enter and exit at the switch in and out of a translation table.
Note that DBT templates whose names contain the word "basic" all have a number of styles defined for switching between different translation tables. (For the list, see Basic Templates.)
References, History and Credits
These tables were initially developed in 1986 by the Institute for the Blind, Worcester, South Africa, with the assistance of Duxbury Systems. They were maintained mainly by Mr. Christo de Klerk with the help of Mr. Jan Bam, and with occasional assistance from Duxbury.
This translator was supplanted by the table for Unified Afrikaans Braille in 2010.
Updates and Errors
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.