kdejute
Forum Replies Created
-
Posts
-
Angela,
No, in a Nemeth transcription of the example you give, an English letter indicator should not be used with the "c". The letter "c" is in regular type, unspaced from a sign of operation (the slash is a sign of operation here).
Cheers!
–KyleCindy,
The arrows certainly seem to have meaning that must somehow be provided for the braille reader. I think the straight horizontal arrows denote an addition number family, and, possibly, the up and right arrows denote a multiplication number family.
Tactile representation would preserve the print's focus on presenting the numbers with spatial relationships.
Still, I think a well worded TN and shapes designated specifically for each kind of number family arrow could get the information to the reader. This might be particularly important if it saves you from inserting scores or hundreds of tactiles. If you use shapes, I suggest that they should be created using Nemeth rules for representing a new shape, and the numbers (including numbers represented by letters) that are part of these families should be in the Nemeth bubble with the shape.
--Kyle
Fair enough. Your question about the "whys" is a good one.
First, "function" in "the function f(x) = 4x-9" is not part of the name of the function, so it is not part of the technical expression.
Similarly, "sequence" in "a sequence t(n)" and "function" in "the function j(x)" are also not part of the NAME of the sequence or function.
Third, "slope" in "a line with slope 3/2" is not part of the technical expression, because a slope does not traditionally have a "proper name" like "Triangle ABC" or "Angle G"; a slope is a value and not a singular item.
Similarly, "x-intercept" in "x-intercept (4, 0)" is not part of a technical expression, because it does not work with the enclosed list to identify a singular item; "(4, 0)" does that by itself.I am not ready to extrapolate universal rules from the above. But do the statements above make sense on their own, and will they help you to wade through material more comfortably?
–Kyle
<p style="text-align: left;">Thank you for the question.</p>
For "1.258 grams per centimeters cubed (g/cm³)." I would enclose "1.258 grams" in one set of Nemeth switch indicators and "(g/cm³)" in another set of Nemeth switch indicators. That second chunk DOES include the parentheses.For "grams (g) of 3 cm³ of the substance at room temperature." I would enclose only "cm³" in a set of Nemeth switch indicators.
I hope that helps! Please post here again if you are looking for further explanation.
Cheers!
--Kyle
I believe you are asking about the Nemeth Code terminator that follows the second tactile graphic in the PDF you attached.
Placing the terminator in cell one would not keep the identifier that follows it from doing its job, I don't think. Nor would that placement prevent the termonator from doing its job.
Since the Guidance specifically says to place the terminator in cell 1, that is really where it should be.
H'lo, Jonathan:
Since what you have is signs of omission surrounded by grouping indicators, and that would qualify as an "enclosed list" according to Nemeth Code definitions, I would advise you to put in Nemeth switch indicators these answer place-holders that are enclosed lists.
Thank you for the question!
--Kyle
In fact, the wording on placement of Nemeth Code indicators around spatial material has changed in the updated Guidance. [Wording that mentions "the margin" was retained for discussion of tables.]
See #8.b under Additional Guidelines on page 9 of the Guidance for Transcription Using the Nemeth Code within UEB Contexts. (http://brailleauthority.org/ueb/nemeth-guidance/Nemeth%20Guidance%20Final.pdf)
The Nemeth Code terminator that follows a spatial arrangement should be in cell 1 on a line by itself, preceded by a blank line.
Thank you for the question, Lynda.
A hyphen as a mark of punctuation does not indicate that material be transcribed in Nemeth. A hyphen is not a modification of a number.
So, neither "8-ounce" nor "10-20 ounces" need be transcribed in Nemeth.
Ah, I see your question.
"72 minutes" should not be transcribed in Nemeth switch indicators. Nor should "72 hours" "72 seconds" or "72 pounds", because the simple numeral "72" falls under the exception described in 3.a under Basic Guidance on When to Switch in the Guidance.
It is not the unit that determines whether a value is technical/mathematical. We determine whether a value is technical/mathematical and Nemeth Code switch indicators are necessary based on what comes before the unit of measure. A decimal, for example, does necessitate Nemeth switch indicators.
Lynda,
In this specific instance, we are saying that "41 minutes 56.23 seconds" is one value and so must be dealt with as a whole. So, because "56.23" must be in Nemeth, the rest of this value must also be in Nemeth.
In other words, "72 minutes" would not need to be in Nemeth. Similarly, "72 minutes 12 seconds" would not have to be in Nemeth.
On the other hand, "43.5 minutes" would have to be in Nemeth. And "43.5 minutes 12 seconds" would have to be altogether in Nemeth.Does that help to make the situation more clear?
–Kyle
I must change part of my response. Some welcome insight from another transcriber leads to the following conclusion:
Although 41 minutes is not in itself technical material, the BANA committee has discussed this and unanimously agrees that the whole expression (41 minutes 56.23 seconds) would be enclosed in switch indicators as opposed to parts of a single expression being transcribed in two different codes. This really is a single expression, not two separate ones.
Thank you for your patience and understanding as we ALL continue to learn about the relationship between UEB and Nemeth Code!
--Kyle
Susan,
Excellent questions. Thank you for bringing these up.
In the first example you describe, only "0.1 mile" should be in Nemeth switch indicators; "per" and "hour" are just words and so should be transcribed in UEB. We would treat "0.5 hour per day" the same way--with only "0.5 hour" within Nemeth switch indicators.
In the second example you describe, really only "56.23 seconds" must be in Nemeth mode. No part of "41 minutes" is technical/mathematical material. Since we do not want to overextend the Nemeth mode, I would say it needs to be restricted to the decimal and its related unit of measure.
The forum did not allow the scan of your example page to upload, because the file was too large, so my response is based only on the, quite well written, text of your question.
Thank you again for laying these examples on the table; you are really helping us interpret and clarify the Guidance.
Cheers!
--Kyle
The ASCII for the appropriate braille for IV.37 is ,,iv".37
The dot 5 is necessary to make it clear that the point-three-seven is not a subscript.
Lynda,
I'm glad you brought this up.
BANA has published two documents providing rules for using Nemeth Code and UEB together. The first was "Provisional Guidance for Transcription Using the Nemeth Code within UEB Contexts" (approved November 2014). The second, and current, is "Guidance for Transcription Using the Nemeth Code within UEB Context" (approved June 2016). This replaces the first publication and is now the only document dealing with using Nemeth Code within UEB that is available from BANA's website. It provides expanded and more honed rules than did the Provisional Guidance.
This Ask an Expert thread was started when only the more brief Provisional Guidance was available, before the release of the current Guidance.
--Kyle
