Lindy Walton
Forum Replies Created
-
Posts
-
Hi Carmen.
The pdf file is not opening for me. From your description, it might be the "barred brackets" depicted on page 123 of the Nemeth Code. I have attached that image. If this does not look like your brackets, can you try attaching your document again?
Lindy
Hi Dani.
Thank you for your question. We suggest that the Nemeth Code terminator be placed in cell 1, following the blank line that is required after the list.
Lindy
Nate, we have been discussing this and have decided that the kindest way to transcribe this is simply to transcribe only the equals symbol in Nemeth. Since it is a Nemeth transcription, the UEB equals sign is not an option. By using the Nemeth symbol, you remain true to the print.
Defaulting to EBAE is not something we should be considering. Use the established UEB symbols and Braille Formats guidelines (Section 20) to transcribe the pronunciation and stress marks.
It wouldn't hurt to explain what you are doing in a transcriber's note, or on the Transcriber's Notes page.
Lindy (and the committee)
( :What an interesting example. Without seeing the rest of the excerpt, I am guessing that this is not being used in "mathematical context". I am going to go out on a limb here and suggest that only the equals sign be done in Nemeth. I welcome a conversation about this.
If you could attach the page so we can see this in context, that would be helpful.
Lindy
Hi Veeah.
The use of boldface in this example is for visual connection between math items. To use boldface indicators in the transcription is messy. I would not use them here. The student can be informed in a TN, formatted as commentary. See the attached brf file for suggested treatment.
Lindy
Example E qualifies as linked expressions using special margins. The last line on the page you sent is a new entry, not as part of the special linked format. The attached BRF file shows how I would transcribe this one. (I assume there is more on the next page, since the verification has not been shown at that point.) Let me know what you think!
LindyAt first glance, this looks like it might require "special margins" according to NC Sec.189.b because the equals signs are vertically aligned in print. But point iii in that section says this: "No sign of comparison, except possibly the first one, may be preceded by any expression on its left." So I took a closer look.
There is something strange about this example. It is actually showing that each step equals cos<theta>, but cos<theta> is not printed after the middle two steps. Your transcription will just fine if you simply insert a general omission symbol after each of those equals signs. Like this:
?COS .?/SIN .?#*?SIN .?/1# .K = _:
and
?COS .?/SIN .?#*?SIN .?/1# .K = _:
I wonder if there are some things missing from the image. Surely the second step ("Simplify by canceling common sine factors.") should have cancellation slashes through each sin<theta>. Could it be printed in a different color that is missing from your source? This would lead me to think that two missing cos<theta>s were also printed in a different color. Of course, you cannot add those items if they don't appear in your copy, but if you find other oddities in this assignment, you might want to investigate the source.
Lindy
Laurie, our recommendation is that the Graphing Calculator Guideline section you quote (6.1) applies only to material shown in a screen. When an expression such as the letter-number combination Y1 appears in the text (not the screen), it is transcribed in Nemeth. A dot 5 between the Y and the number 1 will indicate that the number is printed on the baseline and not in the subscript position.
_% ,Y"1 _:
We are discussing this interesting question! Can you please send an example of what you want to say in your 1-word TN?
Veeah, I think your solution is fine. It is easy to read, once you get the hang of it. Thank you for noticing that the termination indicator is not needed after a shape symbol (unless it is modified). Regarding your last question about the internal termination, I think it reads well. It might be helpful to list that long construction in the list of symbols:
$su_$$33o] Square u-shaped symbol with right-pointing arrow directly over it (Nemeth Code symbol)
With so many transcriber-devised symbols, as well as those uncommon half-bracket symbols, I might suggest pulling out the symbols used in the calculator windows as a separate topic heading on your Special Symbols page. The cell-5 heading could be something like "Nemeth Symbols used in Calculator Windows". Then you can omit "(Nemeth Code symbol)" from each description.
Difficult examples are why we're here. They are fun to analyze and discuss. Thank you for the puzzle.
Lindy
Thank you for pointing out my error. Please back up and read my first response, which I have corrected.
This response has been updated. I have corrected the margins for the displayed expression and have rewritten my response, below.
Hi.
I like your interpretation, except I have questions about the sin function. Section 195.e doesn't give us any guidance about what to do when function notation won't fit on one line. I have been told not separate the function name from its associated "argument" (what comes after the function name--I'm not sure what to call that expression). So I would opt for keeping the grouped expression undivided, as shown in the first way I transcribed this in the attached BRF file. In that transcription, I kept "sin [___]+738" on one line.Others may feel that "390 sin" should not be divided between lines, since it is unspaced in braille. I have shown another option for transcribing this (in the attached BRF file) which divides before the opening parenthesis that occurs inside the bracketed portion.
In neither transcription have I divided again before the plus sign. The practice of making further divisions at locations higher on the priority list has fallen out of favor, and is not stated in the code.
Regarding your question about whether to include the word "latitude" as part of the Nemeth term "60° N", since "60° N latitude" is not part of a math expression, the word is just a word, and so it is correct to transcribe "latitude" in UEB.
I'm glad we are here to help, too.
LindyThis is a formatting detail to which you can apply flexibility, depending on the context and personal preference. You can either treat the proof as displayed narrative and use an indented left margin of cell 3, or you can use full margins (40 cells). Either way, the required blank line before and after the entire proof will set it off from the surrounding itemized material. Another option is to use full margins and add a box. If the box does not exist in print, a TN be appropriate, telling the reader that the proofs are boxed.
If none of these ideas suits your material, please send an image and we can think about other possibilities.
Lindy
