Lindy Walton
Forum Replies Created
-
Posts
-
Hi Beth.
Thank you for your questions.Q#1: About those labels As, Bp, Bs, Cp, Cs, Dp, and Ds. Yes, a 2-letter technical term is to be transcribed in Nemeth. You will use a dot 6 comma since these are not abbreviations.
I would not retain the bold here because the typeform has no meaning other than to catch the attention of the print reader (as far as I can tell. Is there some indication in the text that gives importance to the bold being used?) We are wisely advised to disregard typeform when all instances of the same item are in the same typeform, and/or when the typeform has no technical meaning. Likewise for the bold applied to letters s and p in s = supernatant; p = pellet. The bold is just eye candy here, as far as I can tell. (If you *were to retain boldface for these 2-letter labels, you would treat them as two bold letters, not one bold word.)
To answer your question about indicators, if you were to use the 3-cell Nemeth typeform indicators right next to a code switch indicator, a space is not required between them. The space required before the opening switch does double-duty for the space required before the typeform indicator. Same goes for the terminators.
I want you to know that the upcoming much-anticipated Nemeth Code will have much clearer rules and examples of the use of typeform indicators inside the switches. Likewise, the upcoming much-anticipated Nemeth Code lesson book will reflect the new rules.
Q#2:
Regarding "4,000 x g" etc. OH MY GOODNESS. A little googling brought up the fact that "g" is indeed a unit of measure here (in the context of physics, centrifugal force, and such). It doesn't mean "grams" in this case, but for our purposes just knowing it is a unit of measure helps us know what to do with it. (Space before, ELI needed.) But what about that "x"? We encounter a similar dilemma in "4x6" where the x doesn't really mean "multiply".On this topic, UEB 3.9.1, Crosses, is interesting to read. Yes, you need to determine the meaning of the "cross" sign. UEB says that if the cross is used to show dimensions or degree of magnification, to use the multiplication sign. Okay, then in Nemeth-with-UEB that is our cue to switch to Nemeth because we don't use the UEB multiplication cross in a Nemeth transcription.
So ... put "4,000 x g" all in Nemeth, spacing only before the unit "g". I notice that the print document is inconsistent with their spacing (not an uncommon thing). As long as you are consistent with your intentional treatment of these items, your reader will not stumble.
Here is the link to the meaning of "g", if you're curious: https://www.researchgate.net/post/What-is-the-difference-between-the-G-and-the-RPM-in-Centrifugae-Machine-Is-it-same-or-what-Does-it-have-any-specific-formula-for-conversion
Q#3:
Regarding "1x Laemmli" and "4x Laemmli" etc., yes, this refers to a concentration of a solution. So you need to apply the same logic to this as mentioned in Q#2. Even though 4x is not "math" here, the cross sign requires a switch to Nemeth.Q#4:
Yes, I would assume SDS (on the last line) is an abbreviation. Without any context to rely upon, I would use UEB for SDS, using the capitalized word indicator.Q#5:
When you are doing worksheets, it can be very helpful to obtain a braille copy of the textbook (if available!) or contact the transcriber (if known!) so you can be consistent with what they did.About Handout-9-Table1.jpg: In the context of a table, you can either put just (x g) in Nemeth and switch to NC after the column separation lines, or you can do the entire table in Nemeth, which I recommend. See attached brf file.
Hi Veeah.
The division of expression guidelines are hard to understand, and frankly are not very clear in the code because of the wide variation in issues we face with long expressions.
Over the years, we all got a little carried away trying to make sense of the priority list outlined in the code book.In retrospect, the statement in Lesson 14 that says "If an expression must be divided at a site lower on the priority list, a new line is required at each sign which occurs higher on the list" is simply not practical. You'll be happy to hear that this topic will be easier to comprehend in the updated lesson material and code book, due out some time in 2022. In the meantime...
Honestly, the concept is simple and if we step back a bit, usually we can come up with a clear transcription.
In a long linked expression, the first thing to keep in mind is to begin each link on a new line. There are two links in your example. A new line begins with each of those links, beginning with the equals sign. When the anchor is so small (in this case, "a"), it may seem strange to leave it all alone on a line by itself, but by starting each link on a new line, the structure of the equation is not lost.
The issue now is what to do with the long fraction. Yes, divide before the fraction line, to keep the numerator distinct from the denominator. A numeric indicator is not needed for the "1" in the denominator because it is not preceded by a space.
Now what to do with the factor "9.81 m/s^2"? Since no operation sign is present, you don't need to begin a new line. It's okay if you do, for clarity, but it's not required. If you do begin a new line with "9.81 m/s^2" then you need a numeric indicator before the 9 because it is the first symbol on the line. On the other hand, if you keep "9.81 m/s^2" unspaced from the closing fraction indicator on the previous line, the numeric indicator is not needed.
One correction needed: Delete the space between the plus symbol and "2" in the numerator.
I love your questions. Thank you for sharing this with everyone on the forum.
Lindy
Nate, I didn't mean to leave your question unanswered. I still stand by my original suggestion, using UEB to show the diacritics and Nemeth only for the math symbols (equals sign in this case).
The examples from earlier posts that you found are good to compare the decision-making process regarding which code to use.
1. In the math word problem example from May 2019, (18 kazoos ...), a Spanish eñe occurs in the word piñata. A dot 4 was suggested here, which is a remnant of EBAE but surely works well in this new context and I see no reason not to fall back on this technique. A transcriber's note would explain this use of the dot 4 since Nemeth Code does not define this dot as an accent.
2. In the second example you pulled from July 2021 (geocentric), the use of math symbols in these pronunciations does not in itself make this a "math statement". However, we do not use UEB math symbols in a Nemeth transcription. Since the pronunciation method in this book example uses italics to show stress, transcribing them in Nemeth Code is not a problem to transcribe or to read. Since (46) is more commonly used in math as the Greek-letter indicator, and since (6, 3) is more commonly used as the single-word switch indicator, it might be helpful to mention in a transcriber's note that, within the pronunciations, (46) indicates an italicized word and (6, 3) terminates the italic typeform within an unspaced word.
3. The second example (March 30, 2021) is a nice clear example of using words in a math problem, using Nemeth throughout.
4. Regarding your project, the pronunciation markings provide important information concerning the topic at hand, which is how to pronounce a word. As with example 2, above, the use of math symbols in these pronunciations does not in itself make this a "math statement". However, Nemeth does not have symbols for diacritics. Transcribing diacritics and stress marks is covered thoroughly in UEB, Section 4 and in Braille Formats, Section 20.
I hope this clarifies the decisions made in these four distinctly different scenarios.
Lindy
Rule V of the 1972 Nemeth Code does not have a braille symbol assigned to this "double struck" font. You may use one of the font attributes not used elsewhere in your document, and explain the substitution in a transcriber's note. Usually the script font is the one that transcribers choose to use. So, yes, go ahead and use that indicator (dot 4) before the English-letter indicator and capital indicator for each of these letters. Your transcriber's note can say something like "Double-struck letters are denoted with a dot 4 before the letter indicator."
Lindy
Hi Carmen. Yes, you absolutely *can make a numerator two lines in a spatial fraction. Follow the guidelines for dividing any long math expression to decide where to divide the numerator. Send an image if you would like some help with that.
Lindy
Hi Fred. Thank you for your questions, and for sending us to the Provisional Guidance document for answers.
Yes, "freestanding" includes numbers or letters with punctuation. The example on page 2 of the Guidance shows a UEB number 3 and a UEB letter n with a following period. It is not really necessary to include this information in a transcriber's note, unless your agency or a teacher has asked for it.
I like your solution for rendering the numbered boxes. The numbers are not showing up in your scan, but I get the idea. Regarding the answer choices, I find the terminology "blank section" confusing, but I see that is what it says in the print copy. I'm guessing this test is printed from an online or digital format, which often makes less sense on paper. (The online test-taker probably clicks on their answer choice and it probably will pop into the box in the sentence, I'm guessing.) Regardless, your task is to provide the information clearly to the student. This is really a question for the Braille Formats folks, but I would suggest moving the answer choices to follow each blank in the question, similar to Example 10-19 in Braille Formats. The answer choices are put in parentheses, and you will need to separate the choices somehow. I suggest a spaced slash. This change absolutely requires a transcriber's note. See the attached BRF file for my solution.
I see you are using a square (box) symbol for the scoring numbers. (I assume there is a little box to the left of each slash? It is not showing up in the scan image.) I suggest using UEB there as well, transcribing an underscore instead of a box.
Lindy
Your formatting looks fine. The switch indicators are in a good place. I would suggest numbering the braille pages (in the lower right-hand corner).
I see one little error: You need to correct the numeral 4 in #21.
Thank you for your question.
Lindy
Unfortunately we are not able to open DXB files in this forum. Please save it as a BRF file and I will be able to see it. Thanks.
In a Nemeth transcription, omissions in a math problem are to be shown. If an omission is printed as a "write-on line", the Nemeth long dash is transcribed. For example, in 12 + 7 = __ is transcribed like this:
_% #12+7 .K ---- _:
Does this answer your question? If not, could you attach an example of the worksheet?
Lindy
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
