[
    {
        "role": "user",
        "content": "I%27m%20running%20Duxbury%20DBT%2012.4%20on%20a%20Windows%2010%20PC%2C%20with%20JAWS%20as%20my%20screen%20reader.%20I%27m%20looking%20ata%20.BRL%20file%20in%20the%20Braille%20viewer%20mode.%20While%20I%20can%20ugo%20up%20and%20down%20the%20document%20with%20the%20cursor%20and%20JAWS%20seems%20to%20read%20the%20lines%20correctly%20when%20I%20try%20to%20arrow%20right%20or%20left%20character%20by%20character%20I%20get%20very%20odd%20feed%20back%20from%20JAWS%20that%20doesn%27t%20seem%20to%20match%20up%20with%20the%20line%20at%20all.%20Any%20idea%20what%27s%20going%20on%3F"
    },
    {
        "role": "assistant",
        "content": "Here are some things that could produce the behavior you're seeing with DBT 12.4 + JAWS in Braille Viewer mode. I\u2019ll describe what might be going on, and then give things you can try \u2014 many users have found these help.\n\n---\n\n## What seems to be happening\n\nWhen you open a `.brl` file in DBT\u2019s Braille Viewer (formatted\u2010braille view), you can move up/down lines fine, and JAWS reads those correctly. But when you try to arrow left/right \u2014 character by character \u2014 the speech you get does *not* match the cell under the screen cursor. Often it is:\n\n- Reporting braille cell\u2010codes instead of reading the ASCII characters that the braille represents.  \n- Displaying or reading cells out of sync with what you expect: it may include control codes, formatting tags, or characters not visible on that line.  \n\nThis usually happens in *formatted braille* (rather than \u201cprint\u201d or \u201ccoded\u201d view) when DBT and JAWS are using different assumptions about how the braille cells map to characters, or which line is \u201ctranslated\u201d vs \u201cediting.\u201d It's the mismatch between the underlying braille representation and what JAWS thinks it should say.\n\n---\n\n## Known settings & features that affect this\n\nFrom DBT\u2019s documentation and JAWS scripts for DBT, here are relevant features and how they behave. ([duxburysystems.com](https://www.duxburysystems.com/documentation/dbt%2411.1/JAWS_Scripts.htm?utm_source=openai))\n\n- In **DBT Default Views**, there is a setting *\u201cFont for Translated Braille Line\u201d*. This controls what the on-screen \u201ctranslated line\u201d looks like (e.g. Print / Braille / SimBraille). If the on-screen braille doesn\u2019t match what JAWS uses for its reading table (\u201cBraille encoding for display\u201d), it can lead to mismatches. ([duxburysystems.org](https://www.duxburysystems.org/xhtml/the_menus/MENU_GLOBAL/Global_Default_Views.htm?utm_source=openai))  \n- DBT\u2019s **Internationalization** settings let you set \u201cBraille encoding for Input and Display\u201d \u2014 North American, Unicode, etc. If your `.brl` file came from a different encoding than what DBT is set to use/display, or what JAWS expects, character\u2010by\u2010character navigation could \u201cspeak\u201d cells in a way that seems odd. ([duxburysystems.com](https://www.duxburysystems.com/documentation/Installation_and_Setup_%28Complete%29.pdf?utm_source=openai))  \n- JAWS has *DBT Options* via its \u201cdbtw.jcf\u201d settings (and via quick settings) that affect what is spoken when you arrow left/right in a braille document. For example:  \n  - \u201cSpeaking level for braille lines\u201d \u2014 whether JAWS should stay silent, speak braille characters (dot patterns), or read the translated (print or ASCII) line. ([duxburysystems.com](https://www.duxburysystems.com/documentation/dbt14.1/Content/welcome_to_DBT/JAWS_Scripts.htm?utm_source=openai))  \n  - \u201cSpeak Braille Characters as Local Signs\u201d vs ASCII characters. If this is set to speak \u201cbraille cells\u201d (dot patterns) rather than the ASCII mapping, what you hear might look very unfamiliar. ([duxburysystems.com](https://www.duxburysystems.com/documentation/dbt14.1/Content/welcome_to_DBT/JAWS_Scripts.htm?utm_source=openai))  \n\n---\n\n## Specific likely causes in your setup\n\nGiven what you describe, here are likely culprits:\n\n1. **DBT and JAWS encodings mismatch**  \n   The `.brl` file may use *North American ASCII-braille* encoding (or another local encoding), but your DBT internationalization or JAWS braille encoding might be set to Unicode patterns or some other local set. When you move by character, JAWS will speak the dot pattern (or name) rather than the ASCII character. \n\n2. **JAWS set to speak \u201cbraille cells\u201d rather than ASCII translation**  \n   If JAWS \u201cbraille lines mode\u201d or \u201clevel\u201d is set to speak the braille cell (dot combination) rather than the translated ASCII or print character, arrow left/right will read you dot patterns instead.\n\n3. **The `.brl` file is being treated like \u201ccoded view\u201d**  \n   If DBT is treating the `.brl` file under a \u201ccoded view\u201d context (i.e. with tags, control codes, or DBT\u2019s internal style/formatting codes), then your left/right arrow moves may land you on invisible codes, style markers, etc. JAWS will attempt to speak them, which sounds odd.  \n\n4. **Missing or improperly installed JAWS scripts for DBT**  \n   DBT includes special JAWS-script enhancements to help this integration. If the correct DBT-JAWS scripts aren\u2019t loaded, the behavior can degrade badly. ([sastltd.zohodesk.eu](https://sastltd.zohodesk.eu/portal/en/kb/articles/duxbury-jaws-scripts-installation?utm_source=openai))  \n\n---\n\n## What you can try / how to correct this\n\nHere are things to try. Some may require you to restart DBT or JAWS.\n\n| Action | How to do it / what to check | What outcome to expect if it works |\n|---|---|---|\n| Check DBT's \u201cInternationalization \u2192 Braille encoding for Input and Display\u201d | In DBT, Global \u2192 Internationalization. See if it is set to \u201cNorth American ASCII\u201d or \u201cPrefer Unicode patterns\u201d or something else. If it\u2019s set not to match the `.brl` file, try changing to match the `.brl` file\u2019s encoding. Restart DBT. | When moving left/right, JAWS should speak the ASCII characters or words consistent with the visual text, not raw dot patterns or odd codes. |\n| Look in JAWS Quick Settings (Insert + V) \u2192 DBT Options | Especially: \u201cSpeaking level for braille lines\u201d, \u201cSpeak Braille Characters as Local Signs vs ASCII\u201d, \u201cEchoPC6KeyEntry\u201d. Toggle them to see effects. | You\u2019ll be able to pick what arrowing says: either braille cell dot pattern, ASCII, or \u201csilent\u201d depending on what you want. |\n| Verify correct JAWS scripts are installed for DBT | DBT should prompt when you open it to install its JAWS scripts. Or check the folder C:\\Program Files (x86)\\Duxbury\\<version>\\JAWS for script files. If not installed, install them. If installed but possibly corrupted/outdated, reinstall. ([sastltd.zohodesk.eu](https://sastltd.zohodesk.eu/portal/en/kb/articles/duxbury-jaws-scripts-installation?utm_source=openai)) | With correct scripts, behavior should align: navigation commands operate as expected (JAWS cursor tracking, arrow navigation, etc.). |\n| Check DBT View \u2192 Default Views / Global Default Views | Make sure the \u201cFont for translated braille line\u201d is sensible. Also check whether \u201cShow translated line in braille documents\u201d is on/off. If you have invisible print translation or something off, that can influence how JAWS reads. ([duxburysystems.org](https://www.duxburysystems.org/xhtml/the_menus/MENU_GLOBAL/Global_Default_Views.htm?utm_source=openai)) | You\u2019ll see on screen what line DBT considers translated (ASCII vs braille) and JAWS will align its spoken feedback accordingly. |\n| Open the `.brl` file via \u201cFormatted Braille Importer\u201d vs normal open | When importing, there's often an option \u201cRead formatted braille without interpretation.\u201d If the file has formatting which DBT is trying to interpret, turning this on will make DBT leave the `.brl` content raw. ([duxburysystems.org](https://www.duxburysystems.org/dbtwebhelp/content/miscellaneous/brf_files.htm?utm_source=openai)) | Raw content avoids DBT inserting codes or changing spacing; JAWS should then read exactly what\u2019s there, making arrowing more predictable. |\n\n---\n\nIf you like, I can walk you through *your specific settings* step by step (for DBT and for JAWS) to get arrow-navigation to give you the ASCII/print (or whatever you want) rather than weird cell outputs. Do you want me to guide you through that?"
    },
    {
        "role": "user",
        "content": "Yes%20walk%20me%20through%20the%20steps%2C%20as%20a%20screen%20reader%20user."
    },
    {
        "role": "assistant",
        "content": "Here\u2019s a step\u2010by\u2010step guide you can follow using only your keyboard and JAWS to try to fix the mismatch you get when moving left/right in a `.brl` (formatted braille) document in Duxbury DBT 12.4. I\u2019ll include both the DBT side and the JAWS side. If possible, you may want a second device or another person to help check visually\u2014but this is designed so you can do it all with screen reader and keyboard.\n\n---\n\n## Steps inside DBT (Duxbury)\n\nThese steps will help make sure DBT is using the right encoding, showing translated lines, and not confusing formatting codes with visible text.\n\n1. Start DBT, if not already open, and open your `.brl` file.\n\n2. **Check Internationalization settings: encoding and UI Automation**\n\n   - Press ALT + G to open the **Global** menu.\n   - Use arrow keys to find **\u201cInternationalization\u2026\u201d**, then press ENTER.  \n   - In that dialog, find **\u201cBraille Encoding for Input and Display\u201d**, see if \u201cLocal/National Encoding\u201d (for you likely *North American English*) is selected, or whether \u201cPrefer Unicode Braille Patterns\u201d is selected. ([duxburysystems.com](https://www.duxburysystems.com/documentation/Installation_and_Setup_%28Complete%29.pdf?utm_source=openai))  \n   - Also look for a check box such as \u201cUse Local/National Encoding for all Braille Display\u201d. If available, make sure this is what your encoding aligns to rather than Unicode patterns.  \n   - While in this Internationalization dialog, also check for **Support for UI Automation** \u2014 many users recommend *unchecking* that box when working in DBT with JAWS. ([duxburysystems.com](https://duxburysystems.com/documentation/dbt14.1/Content/welcome_to_DBT/JAWS_Scripts.htm?utm_source=openai))\n\n   If you make changes, press TAB until you reach OK, then press ENTER.\n\n3. **Set your Default Views so the translated line and fonts are appropriate**\n\n   - Press ALT + G, arrow down to **\u201cDefault Views\u2026\u201d**, press ENTER.  \n   - In the Default Views dialog, you should find:\n\n     \u2022 \u201cFont for Translated Braille Line\u201d \u2014 options: *Print*, *Braille*, *SimBraille*. Choose *Print*. This way the translated (print/ASCII) text shows at bottom (translated line), which helps align what you hear left/right with what you expect visually. ([duxburysystems.org](https://www.duxburysystems.org/dbtwebhelp/content/the_menus/menu_global/global_default_views.htm?utm_source=openai))  \n     \n     \u2022 \u201cDefault font for braille documents\u201d \u2014 also select *Print*. (So the on\u2010screen cells are shown in ASCII rather than dot graphics, which can confuse left/right navigation.) ([duxburysystems.org](https://www.duxburysystems.org/dbtwebhelp/content/the_menus/menu_global/global_default_views.htm?utm_source=openai))  \n\n     \u2022 Ensure \u201cShow translated line in braille documents\u201d is checked. That gives you a bottom line which is the print equivalent of the current braille line under the cursor. ([duxburysystems.org](https://www.duxburysystems.org/dbtwebhelp/content/the_menus/menu_global/global_default_views.htm?utm_source=openai))  \n\n   - Move with TAB to OK, press ENTER to confirm.\n\n4. **Use Formatted Braille Importer options BEFORE opening the `.brl` file (if it was imported, or if you import similar files later)**\n\n   - ALT + G \u2192 arrow to **\u201cFormatted Braille Importer\u2026\u201d**, ENTER. ([duxburysystems.com](https://www.duxburysystems.com/documentation/dbt%2412.1/the_menus/MENU_GLOBAL/Global_Formatted_Braille_Importer.htm?utm_source=openai))  \n   - At top, check the box \u201cRead formatted braille without interpretation.\u201d This tells DBT *not* to try to interpret formatting/layout codes in the `.brl` file; instead it treats `.brl` content more literally. ([duxburysystems.com](https://www.duxburysystems.com/documentation/dbt%2412.1/the_menus/MENU_GLOBAL/Global_Formatted_Braille_Importer.htm?utm_source=openai))  \n   - Also set \u201cCells per line on input page\u201d and \u201cLines per page\u201d appropriately if the `.brl` file is formatted, so DBT knows how to break the content. But the unresolved interpretation often causes weird feed when left/right arrows go into hidden codes or control spaces.\n\n   - Press OK once settings are right.\n\n---\n\n## Steps inside JAWS (Quick Settings / DBT options)\n\nThese are the settings that control what JAWS *speaks* when you move through lines or cells in braille documents.\n\n1. While in DBT, press **Insert + V** (JAWS Quick Settings). The first part should be **DBT Options**. ([duxburysystems.com](https://www.duxburysystems.com/documentation/dbt14.1/Content/welcome_to_DBT/JAWS_Scripts.htm?utm_source=openai))\n\n2. In that DBT Options area, cycle through options (use arrow keys) to find:\n\n   - **\u201cSpeaking level for braille lines\u201d** \u2014 this determines whether arrowing left/right speaks nothing (`silent`), speaks each braille cell as dot patterns or characters, or speaks the translated (print) equivalent.  You\u2019ll want \u201cread the translated line\u201d so that as you move cell by cell, JAWS tells you the ASCII / print character instead of raw braille cell. ([duxburysystems.com](https://www.duxburysystems.com/documentation/dbt14.1/Content/welcome_to_DBT/JAWS_Scripts.htm?utm_source=openai))  \n   - **\u201cSpeak Braille Characters as Local Signs vs ASCII\u201d** \u2014 this option lets you choose whether to hear signs (dot\u2010based identifiers) or ASCII characters. For `.brl` documents where you expect print characters, set this to ASCII. ([duxburysystems.com](https://www.duxburysystems.com/documentation/dbt14.1/Content/welcome_to_DBT/JAWS_Scripts.htm?utm_source=openai))  \n   - **EchoPC6KeyEntry** \u2014 this controls how keyboard entries (like six\u2010key braille typing) are echoed. If toggling this influences left/right moves, ensure it's set so that you hear constructed braille characters appropriately. ([duxburysystems.com](https://www.duxburysystems.com/documentation/dbt14.1/Content/welcome_to_DBT/JAWS_Scripts.htm?utm_source=openai))\n\n   Toggle each of those (by pressing SPACE or as instructed) to get the behavior you want.\n\n3. If any settings have Alt + key toggles (like Alt + U, Alt + P, etc.), try those out once above to see effect quickly. For example, Alt + U toggles the \u201cSpeaking level for braille lines\u201d (silent / braille cells / translated line). ([duxburysystems.com](https://duxburysystems.com/documentation/dbt14.1/Content/welcome_to_DBT/JAWS_Scripts.htm?utm_source=openai))\n\n---\n\n## Test and adjust\n\nAfter making those changes above, try these tests:\n\n- Arrow up/down a few lines. You should hear the translated line at the bottom speak consistently, and moving up/down should read you the print or ASCII translation of the braille line.\n\n- Arrow left/right cell by cell. Now, instead of odd cell codes, you should hear the ASCII letters (or print translation) matching the character under the cursor.\n\n- If you still hear odd feedback (braille cell patterns, or control codes), go back and check:\n\n  1. Did you use *Print* font for translated line and braille font? If \u201cBraille\u201d or \u201cSimBraille\u201d is selected, you\u2019re still in dot mode.\n\n  2. Is JAWS\u2019s speaking level for braille lines set to \u201cread translated line\u201d? If not, you\u2019ll hear cell dot patterns.\n\n  3. Check whether \u201cRead formatted braille without interpretation\u201d is on (if the file is formatted). When off, hidden codes or spacing may be interpreted by DBT, interfering with mapping.\n\n---\n\nIf you want, I can show you the exact set of keystrokes to *export* or *view* the file in a \u201cpure\u201d mode (plain ASCII, no codes) for proofreading \u2014 that tends to eliminate surprises and mismatches. Do you want to walk through that?"
    }
]