[Michael Gunner]

Hello Lealisa,

I am uploading a quick reference sheet.

Let me know if this works for you.

Mike

Attachments:

You must be logged in to view attached files.

[Michael Gunner]

I will reach out to the committee and get back to you.

[Michael Gunner]

Hello Katy,

Thank you for your question.

Once you have determined to keep the bold font, follow Rule 6.3.4 of the Nemeth Code.

Mike

[Michael Gunner]

Hello Delores,

Thanks for the question!

In this situation you are incorrect to close and then reopen the Nemeth code indicators. There is nothing in the tactile that requires a switch back to UEB.

Mike

[Michael Gunner]

the other page

Attachments:

You must be logged in to view attached files.

[Michael Gunner]

Hopefully this works better.

Attachments:

You must be logged in to view attached files.

[Michael Gunner]

Hello,

Since the R is connected to the number, they are modified. Modified numbers need to be transcribed into Nemth code.

Mike

[Michael Gunner]

Hello,

Thank you for the question.

In looking at your example, the text states to use the linear regression command on a graphing device. As I researched this topic, I found that the linear regression command on a scientific calculator is “LinReg”. To get there, you click STAT, then CALC ….

Based on this information, the words linear regression will not appear on the screen, and you should transcribe contracted in UEB using a transcriber-defined font for the sans serif.

Mike

 

[Michael Gunner]

Thank you for the question.

Based on NC 26.3.5, the division of units of measure between lines applies to numbers, letters, and their associated abbreviation.

In your example, the inclusion of the word kilometers separates the two units. This allows you to divide between lines.

Mike

 

[Michael Gunner]

Happy Thursday,

Thanks for the question.

Option 3 is the best choice. While there is no hard and fast rules addressing your example, the 71 does not need to be in Nemeth code. Placing the opening indator after the 71 is the best option.

Mike

[Michael Gunner]

Hello,

That is a good question and can definitely be a cause for confusion.

Under the rule in section 4.6.4 of the Nemeth Code, you can choose the code that works best for your numbers. In this case, because the numbers are unmodified, UEB is the appropriate choice. As these numbers are considered UEB text, applying the UEB guidelines is the correct choice. (NC 26.4.2)

Mike

 

 

 

 

[Michael Gunner]

Hello Cheri,

Thank you for your question. You are touching on a frustrating aspect of Nemeth w/UEB transcriptions.

The rules governing code-switching and when to use them can be found in Rule 4 of the Nemeth Braille Code for Mathematics and Science Notation 2022. Further explanation can be found in AN INTRODUCTION TO BRAILLE MATHEMATICS USING UEB WITH NEMETH A Course for Transcribers Second Edition, 2025—specifically Lessons 1 and 4.

For your example, the words you are using to represent the shapes would just be transcribed in UEB unless they were in the Nemeth code switches.

Please see the attachment for how your examples would be transcribed.

Mike

Attachments:

You must be logged in to view attached files.

[Michael Gunner]

Hi Gala,

The consensus of the committee is as follows:

Print should be followed and a long dash used to represent the printed underscore. If space is an issue, then the alternative choice would be a general omission symbol with a TN.   We do <i>not</i> recommend the use of the short dash as NC 25.8.3.d specifically reserves its use for blank entries (i.e., blank spaces) in print.

Thanks

Mike

[Michael Gunner]

Hi Gala,

I am sending this question out to the committee. Once we have a consensus, I will provide you with an answer.

Mike

[Michael Gunner]

Hello,

Since this material is not text, I would follow the example you referenced from the puzzle section of Braille Formats.

Mike

[Author]

Posts