Lindy Walton
Forum Replies Created
-
Posts
-
You are very welcome! I forgot to mention that, if you use CBC, you should cite it on the Transcriber's Notes page as follows:
Computer Braille Code, Revised 2000, 2010 Update
and you should mention on the Special Symbols page that the non-UEB code switch indicators are switching to that code.
Here is our recommendation.
As mentioned before, computer code should not be transcribed in Nemeth. But since your client insists, it would be better to use the old Computer Braille Code for the computer text. This would be an interesting mix of UEB, Nemeth, and CBC, and is not standard practice, but we feel it would be better than trying to wrestle Nemeth Code within the computer language. You would precede and follow the computer notation with the "non-UEB" code switch indicators. See Section 14 of the Rules of Unified English Braille.
IF you continue to transcribe the computer notation in Nemeth, the number following the percent symbol needs to be identified as a numeral, so a numeric indicator should be inserted.
Let me know if further problems arise.
- Lindy Walton
I will run this by the BANA Nemeth committee and see what they have to say about the unspaced numeral following a percent symbol.
I'm sorry that your expertise as a Nemeth transcriber is not being respected here -- you should not be transcribing the computer notation in Nemeth.
Hi Carmen.
I'm not quite sure what to say. If you are transcribing Javascript, you should be using UEB. Computer notation does not use Nemeth Code. Can you send an image of what you are dealing with?
Thanks.
- Lindy
Hi Marcellina. This is something I am not familiar with. Is there a reason the dot 3 apostrophe would be unclear or ambiguous?
My second thought is to use a dot 6 comma and explain it in a transcriber's note, but if the comma symbol is being used for a decimal point, then this would not be an option.
Is there anyone out there who has a solution?
- Lindy
Hello. I apologize for the delay in my response. I have been away.
The sample pages you sent are in UEB. If you are transcribing technical material in UEB, you should not be following the rules in the Braille Code for Chemical Notation -- that resource is an adjunct to the Nemeth Code.
I am not at all an expert in UEB technical. I suggest that you post your question to the UEB Technical thread. Please include an image of the print for this chemical diagram. The best advice can be given when the print is shared.
Thank you for your question. I will learn something when I read the reply.
- Lindy Walton
Hi Beverly.
Actually, there is nothing on this page that requires Nemeth. Use the UEB low line (underscore) for the blanks, and contract the word "and".
.- & .- IS .-4
In another setting, regarding the use of the single-word switch indicator in Nemeth context, although its use is limited to only one word at a time, it can be used more than once in a sentence as long as there is Nemeth between them.
Lindy
How interesting!
Since the perpendicular sign is not functioning as a comparison sign here, you are correct to transcribe it as you would any other subscript.
_% R;$P",F _:
Hi Katrina. The negation symbol you have described is one of several symbols used in logic to denote negation. Since this particular print sign is not listed in the Nemeth Code, you can replace it with any of the other negation symbols as long as you explain in a transcriber's note, and as long as the symbol you choose is not also used in print in this context. I have attached an image from Wikipedia that shows other options. The tilde would be my first choice. "Np" would be my second choice.
Please let me know if you need further advice.
Lindy
Hi Cheri. Thank you for your question. This is an interesting example because one of the column headings does indeed require Nemeth, and the row headings are words.
As with any table, there is more than one way to transcribe this. My first priority when setting up a table that will be used in a classroom setting is to have the layout match print as much as possible. The second priority is not to overuse keying or transcriber's notes, since that tends to take the reader's attention away from the table itself.
In this table, the issues are not really the row headings. There are only two contractions in those words, so transcribing them in UEB or in Nemeth doesn't change the spacing issues.
Here is what I would do with this table. Write a transcriber's note that "x" means "Partner 1(x)" and that "y" means "Partner 2(y)". Now all you need to do is switch to Nemeth for the "d-squared" column heading. See BRF example, attached.
I don't know why there is no space between 1 and (x), between 2 and (y). I followed print and I transcribed 1(x) and 2(y) in UEB.
Lindy
HI Deborah.
The Nemeth Code does not have a symbol for the "down tack". You get to devise one! I'll ask for some advice and get back to you soon.
Lindy
It sounds like you have the right idea. The decision whether or not to switch to Nemeth for a graphic is the same, really, as switching decisions within the narrative. A tactile graphic is not in any "code" per se -- it is the braille symbols associated with it, such as labels or keyed items, that obey the rules of UEB or Nemeth, as appropriate.
There are spacing issues in a graphic, however. If the labels can all be done in UEB, do so. If, however, a label requires a switch to Nemeth, it is ideal to place the switch indicators out of the way of the graphic -- that is, open Nemeth, blank line, graphic (with Nemeth labels), blank line, terminate Nemeth (if needed).
This will encompass the entire page only if the drawing itself takes the entire page. If the page has text before the graphic, open Nemeth after the text. The opening Nemeth Code indicator can go on the same line as the narrative, but if it doesn't fit, put it in cell 1 on the next line. The blank line the precedes the graphic will be on the following line.
An exception is made regarding Cartesian graphs, which may be transcribed without the use of code switch indicators as long as the omission is clearly stated on the Transcriber's Notes page.
Code switching needs to be considered individually with each graphic.
Lindy
Don't you just love puzzles? If I understand this right, the four answer choices (T A L E) are shared among the three questions (1 2 3). I expect the instructions come first and perhaps apply to several problems in the riddle puzzle?
Braille Formats Section 10 gives guidelines for exercise material. I'm sure you've read them. I think you need to be creative with your worksheet.
I would draw the triangle first, followed by the four shared answer choices (listed in cell 3), then the three questions (listed in cell 1). Keep it all together on the same page. Disregard the circles around the letters and numbers.
I'll sketch it out, below. (You will use the horizontal-fraction-line fraction style shown in your image.)
(switch to Nemeth)
-----------blank line
[graphic]
-----------blank line
T 12/13
A 5/13
L 13/5
E 5/12
-----------blank line
1 sin A
2 cos A
3 tan A
-----------blank lineIf your layout doesn't seem clear to the reader, compose a short transcriber's note. Something like "Four lettered answer choices are given before each set of numbered questions."
Another idea is to insert "Answer Choices" as a transcriber's note before each list of answer choices and "Questions" before each list of questions. The TNs in cell 5 (like a cell-5 heading) and each list in cell 1. This would require a lot of code switching, however, since the TNs must be in UEB.
You might like to run your question by the Braille Formats forum and see what other folks suggest.
Thanks for your puzzling question.
Lindy
The BANA Nemeth committee is advising that you follow UEB rules and use UEB symbols for web addresses.
On your Special Symbols page, I suggest specifying the context in which the UEB "math" symbol is used. For example, "Equals sign used in web address"
Lindy
I'm happy to see your question because there has been much misinterpretation of this rule. Current recommendations under discussion are that you need not divide at every location "higher on the priority list". Regarding the example you sent, you are correct that the (red) baseline indicator attached to the plus symbol should begin the runover line, however it is not necessary to divide again before the final addend (blue). The second example (Example 15.16-4 in the Provisional edition of the Nemeth lesson manual) shows a grouped expression that will not fit on the line. In my opinion, it does not need to be divided further. It is not necessary to divide before the division symbol.
You will be happy to know that the upcoming new edition of the Nemeth Code and the upcoming new edition of the Nemeth instruction manual will be presenting much clearer guidelines to follow when faced with a long mathematical expression that requires division between lines. Until their release, I am happy to address your questions in this forum.
Lindy
