DBT codes

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #38909
    smart_10357
    Participant

    Hi Kyle

    I have some questions about the dbt codes I use in Nemeth for use in UEB. I do not know if this is the space I should be writing in so I am going to send you a word document to your aph email to see if you can help me. The NBA format will not let me cut copy and paste a word document. It turns it into ascii.

     

    Thanks Susn

    #38917
    kdejute
    Moderator

    Susan,
    Together, we found some useful reminders and DBT tools! For future reference, a brief summary of what came out of our email exchange is below.
    We must remember to use braille grouping indicators to limit the effect of a bar over previous item indicator when necessary. (See webinar "Decimals, Including Repeating Decimals")
    We used the following DBT codes in Word when preparing a file for DBT (Duxbury Braille Translator). Code "names" are my personal designations, not official names.

    • fs – fraction start ... We used this to code the start of any fraction (numeric or general; it works for both).
    • fl – fraction line ... We used this between any fraction's numerator and denominator.
    • fe – fraction end ... We used this to code the end of any fraction.
    • ts – technical start ... We used this to get a grade 1 passage indicator.
    • te – technical end ... We used this to get a grade 1 terminator. The ts and te code pair seems to sometimes repress grade 1 indicators between them.
    • g1 – grade 1 ... When paired with g2, we used this to suppress grade 1 indicators when we did didn't need them (because numeric mode had already turned on grade 1 mode).
    • g2 – grade 2 ... We used this paired with g1 to enclose material in which we chose to suppress grade 1 indicators.
    • : – protect group start ... We used this paired with ; to enclose material that we wanted to stay all together on one braille line.
    • ; – protect group end ... We used this paired with ; to enclose material that we wanted to stay all together on one braille line.
    • e – begin modified expression ... We used this to code the start of any material that is modified by having something (e.g., a bar) directly over it.
    • bar – bar over (I think) ... We used this after the modified expression (e.g., "63" in the example below) to code what thing was modifying the modified expression
    • ac – We used this before the "bar" code when we needed to get braille grouping indicators to limit the effect of the bar over previous item indicator.

    For fun, here are some of the symbols-sequences we were working toward.</p>
    #dj/aa "7 #c4<#fc>: 3.63 with a single bar over "63"</p>
    ;;;(a./b)"6(c./d)
      "7 (ad./bd)"6(bc./bd);' “‘fraction a over b’ plus ‘fraction c over d’ equals ‘fraction ad over bd’ plus ‘fraction bc over bd’”

    • This reply was modified 1 month ago by Chris Clemens.
    • This reply was modified 1 month ago by Chris Clemens.
    • This reply was modified 1 month ago by kdejute.
    • This reply was modified 1 month ago by kdejute.
Viewing 2 posts - 1 through 2 (of 2 total)

Everyone is free to read the forums, but only current NBA members can post. Become a member today. Click here to Login and return.