James Williams
Forum Replies Created
-
Posts
-
After polling both the CAT and TG committees, we have come to the conclusion that all three programs mentioned have the tools to make a tactile graphic, with each working basically the same with the only differences being in the user interface. The primary thing to remember is keeping in mind the output method and creating the tactiles from that point of view rather than which software is used.
One committee member also mentioned that, at least in the past, the Index Basic D came with TactileView and the Juliet 60 came with Firebird, so consider researching that software when either creating or proofing tactiles.
As for specifics, unfortunately, there is not much more we can offer. As with all things in life, sometimes trial and error is the best method for proceeding.
Hopefully you will find something helpful in our response.
Sorry for the delay in responding, but I wanted to ask your question of both the CAT and TG Committees to provide a balanced response.
In regards to possible software to use when producing graphics, there are several options available, including but not limited to: Inkscape (.svg files), CorelDRAW, Adobe Illustrator, Microsoft Word, and Viewplus' Tactile Software Suite (TSS). Each has their own merits in regards to which type of graphics you will primarily be producing (technical, literary, etc.). The major thing both committees wish to stress is to base the creation of your graphic (software used) on the output method (embosser).
As for preferences for TGs produced using different methods, these will vary based on the experiences of each individual braille reader. Some prefer graphics produced on a braille embosser and enhanced with collage elements, while others prefer SwellBraille or simply the unmodified dots produced on an embosser such as those produced by ViewPlus.
Both committees encourage you to discuss with your student(s), if possible, the methods preferred for graphics production and go from there.
I hope this helps!
My apologies for not responding sooner, but I was out of town at the NBA Conference.
This question would be better posed to the Tactile Graphics Committee as they have better insights into the processes for these three tactile-specific programs. I have forwarded your question to that committee.
James
I have passed your question along to the members of our committee. As soon as we have an answer, I will post it.
To my knowledge, one of the few ways to insert graphics into a Duxbury files consists of using Duxbury's free QuickTac program. The latest version is 4.1 and information about it can be found under the Products section on Duxbury's website. I have not used this program for any graphics I have produced and honestly haven't even explored its features that much.
I typically use CorelDRAW for all of my graphics, paste the braille into the graphics file and send two separate files to the customer.
In the future, with the eBraille initiative, the idea is to combine the graphics file and braille file into one eBraille file to avoid sending so many separate elements to the customer/reader. More information can be found about the status of that project in this NBA webinar from June: https://www.nationalbraille.org/resources/webinars/2024-ebraille-update/.
The simplest way to do what you are asking is to open a separate DXB and six-key your braille in that document. Once you have brailled what you desire, then you copy that and insert it into your DXP within the codes [cz] and [tx], which begin and end exact braille translation where ASCII input is translated to braille output. These can be inserted via the keyboard shortcut F9; just type the first code, hit enter, press F9 again, type the second code, and hit enter. You can use the <ExactTranslation> style, but directly using the codes sometimes works better than working with a style, especially with more complex constructions.
If you know the ASCII equivalent for your desired symbols, then you can just type those within the [cz] and [tx] codes without having to six-key your braille.
Also, modified expressions can be inserted in your document using codes, which cuts out the hassle of six-keying your braille. For your example of the modified sigma, the code string would be [e]σ[bar], which would give you a sigma with a bar over it. [e] signifies that what follows is a modified expression; the sigma was inserted from Layout: Code List menu, or keyboard shortcut F5; and [bar] inserts the bar above in this instance. All of these codes mentioned in this post can be found within the Layout: Code List menu and are explained within Duxbury's DBT Code Quick Reference article found within the Help menu.
Please forgive the length of this response, but I thought I would give you a couple of options to explore and consider when inputting mathematical/technical materials in Duxbury. I hope this helps.
After conferring with the committee and reaching out to Duxbury, the closest thing to a comment placed in the text would follow the tilde in the [idle~] code. Since no spaces are allowed within codes, you would have to separate each word with an underscore. For example, if you wanted your comment to read, "text to be deleted," then the code would be entered as [idle~text_to_be_deleted].
Also, there does not seem to be a limit as to the length of the text following the idle code. Therefore, you could write your code with the words unspaced and using title case, as in [idle~25Lines38CellsInterpointEmbossBraillo].
When the DXP is translated to a DXB, the text within the code does not appear within the braille document. You will have to include spacing around the code, otherwise your braille text will run together since the translator ignores the [idle] command.
Hello, Julie!
If you are beginning in Word, apply the Spanish style to your Spanish text. Whether you are using Swift or have attached the BANA template to your document via a macro, the Spanish style is represented by the red capital S on the Braille or Add-ins ribbon. You can also use keyboard shortcut Alt+Shift+S to apply it to the highlighted text.
Text within this style will be uncontracted and use Spanish braille symbols for the modified letters (punctuation, however, will remain in UEB) when the Word document is opened in Duxbury. If you accidentally insert the style on your English text, then it will be uncontracted, so make sure you are just applying the Spanish style to your Spanish text and the English portion should remain contracted. Hope this helps!
James
Here is the response from one of our Braille2000 experts:
Use Ctrl+F, type in the opening TN indicator. Above the search bar, click Extend. Type the closing TN indicator. Click Extend All. This should highlight all TNs in the volume. Finally copy them.
We hope this helps!
